No description
The "Plot path to beacon" action now includes `tx_power_dbm` and `src_gain_dbi` in the /path query string so the path calculator's TX side emits the same EIRP as the beacon out of the box. The beacon schema stores `power_mw` as EIRP already (per Beacons.RangeEstimate), so we take 10·log10(power_mw), split against a default 30 dBi dish, and clamp the TX power to a 0 dBm floor so very-low-EIRP beacons produce a sane gain/power split instead of -10 dBm outputs. Examples: 10 W EIRP (40 dBm) → 30 dBi dish + 10 dBm TX 100 W EIRP (50 dBm) → 30 dBi dish + 20 dBm TX 100 mW EIRP (20 dBm) → 20 dBi + 0 dBm (clamped) |
||
|---|---|---|
| .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