尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Live portal for the Shellfish Hardening & Organismal Resilience Experimentation Center (Roberts Lab, UW). Published at https://robertslab.github.io/shore-line/.
| Widget | Source | Refresh |
|---|---|---|
| Live Tankcams | gannet v1_web/webcam/latest.jpg and v1_web/webcam_02/latest.jpg (Last-Modified header), plus live HLS video from v1_web/webcam_03/stream.m3u8 (native HLS, else hls.js; hls.js needs gannet to send CORS headers) → data/webcam.json | site rebuild every ~10 min; page re-polls every 60 s |
| Puget Sound water temp | NOAA CO-OPS (Tacoma 9446484, fallback Port Townsend) → data/field-water.json + assets/water-banner.svg | every rebuild |
| Water-quality reports + per-tank readings | genefish RSS (Jesse Lowe) → data/reports.json | every rebuild |
| Facility temperatures | data/tanks.json (setpoint); one card, the Seneye Tank (Left Blue), live from a seneye → seneye-data branch → data/seneye.json; plus one card per DS18B20 probe on the ESP32 hubs, from Gannet's raw CSVs (SHORE_temps/data/raw/<hub>/) → data/shore-temps.json (names in tanks.json → probes) | seneye every 15 min; probes every rebuild |
| Research from SHORE | data/research.json (hand-curated) | — |
A static site (index.html, css/, js/) with no build step.
.github/workflows/site.yml runs every 10 minutes. It fetches the live sources with the stdlib-only scripts in scripts/, writes the results into _site/, and deploys to GitHub Pages. Fetched data is not committed. If a source is down, the script republishes the copy that is currently live and marks it with an error, and the status dot for that feed turns amber or red.
The Seneye Web Server sits on a private UW address (172.25.149.26), which GitHub can't reach. So scripts/collect_seneye.py runs on a machine inside the network. It decodes the SWS WebSocket state, which has no JSON API, and keeps a 14-day series. scripts/seneye_publish.sh force-pushes that file as a single commit on the seneye-data branch. The site build mirrors it from the SENEYE_URL repo variable.
/tmp/shore-seneye.log.scripts/install_seneye_agent.sh
launchctl unload ~/Library/LaunchAgents/com.robertslab.shore-seneye.plistseneye_publish.sh from cron there. Alternatively, write the JSON to a web-served path and point SENEYE_URL at it.null for those instead.items in data/research.json (featured: true puts it in the top cards, max 3). Remove the placeholder entry once there's a real one.data/tanks.json. Set status to anything other than placeholder and fill latest / series when a logger feed exists.WEBCAM_URL, REPORTS_FEED, SITE_LABEL.python3 scripts/update_webcam.py && python3 scripts/update_reports.py && python3 scripts/update_field_water.py
python3 -m http.server 8320
Then open http://localhost:8320. update_field_water.py --demo uses synthetic data when you have no network.
See PLAN.md for the roadmap.