No description
Replaces the "tropo composite + post-hoc aurora boost" model with a max-over-mechanisms dispatcher so each band's score reflects the dominant propagation channel rather than summing alternative paths. - BandConfig.mechanisms/1 derives the stack from frequency: ≤432 MHz gets [:tropo, :aurora]; >432 MHz stays [:tropo]. Bands may override with an explicit :mechanisms field. - Scorer.mechanism_score/3 returns a standalone integer score for one mechanism (:tropo delegates to composite_score; :aurora is a clean Kp/freq function, not a boost on top of tropo). - Scorer.cell_score/2 takes max across the band's mechanisms so a Kp-6 storm scores 6m at 85 even when the tropo picture is poor, instead of conflating the two channels. Es and F2 stay in PathCompute since they're path-distance-dependent. The legacy aurora_boost path is unchanged so no callers shift today. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| rust/prop_grid_rs | ||
| scripts | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| bugs.md | ||
| CLAUDE.md | ||
| Dockerfile | ||
| Dockerfile.base | ||
| elevation.md | ||
| LICENSE | ||
| 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