No description
The "Updating propagation +Nh" chip was double-misleading in prod: the label's +Nh was relative to the HRRR run time (which lags wall clock by ~2h), and the progress broadcast fired before the hour was fetched + persisted — so the chip could read "+8h" while the map timeline only extended to +4h. Reframe the label as "through now" / "through +Nh" / "through Nh ago" by computing the offset from valid_time → now in PipelineStatus. running_detail, so it matches the semantic the user reads off the timeline. Move the PubSub broadcast in PropagationGridWorker to fire after Propagation.replace_scores/2 succeeds, so the chip only advances once that forecast hour is readable from ScoresFile. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| scripts | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| CLAUDE.md | ||
| Dockerfile | ||
| elevation.md | ||
| mix.exs | ||
| mix.lock | ||
| prediction.md | ||
| README.md | ||
| tail_logs.sh | ||
| updates.md | ||
Microwaveprop
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix