Fix typos and note meteorologist help in prop1 post
This commit is contained in:
parent
a157470785
commit
440553824c
1 changed files with 6 additions and 4 deletions
|
|
@ -57,8 +57,8 @@ have now been backfilled with this information. Feeding all of this in to Claude
|
|||
[algorithm](https://prop.w5isp.com/algo) that understands and can predict future conditions based
|
||||
on weather data.
|
||||
|
||||
This algorithm gets turned in to code, and then we can fetch HRRR data hourly, ammend with ASOS
|
||||
when avaliable and feed it through the algorithm to determine if any given area's atmosphere is
|
||||
This algorithm gets turned in to code, and then we can fetch HRRR data hourly, amend with ASOS
|
||||
when available and feed it through the algorithm to determine if any given area's atmosphere is
|
||||
favorable to propagation. Our predictions are still estimated and may not have any bearing on
|
||||
reality.
|
||||
|
||||
|
|
@ -67,5 +67,7 @@ to refine our prediction model gradually over time. Another sub-project is autom
|
|||
monitoring. Any NLOS beacon that can be automatically monitored continuously provides an enormous
|
||||
amount of data to train our model with since both points are known.
|
||||
|
||||
If you'd like to help out, we need as many contacts during non-contest times as possible and future
|
||||
automated beacon monitoring. You can reach me at my first name at my last name dot me (it's in the footer.)
|
||||
The effort to expand has been growing and we now have help from a senior meteorologist in Lubbock,
|
||||
Tx and many hams helping submit verified contacts. If you'd like to help out, we need as many
|
||||
contacts during non-contest times as possible and future automated beacon monitoring. You can reach
|
||||
me at my first name at my last name dot me (it's in the footer.)
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue