-
Notifications
You must be signed in to change notification settings - Fork 0
Raw data text UI #11
Comments
@kg4sgp expressed interest in this. I'm not sure if he was interested in hacking on it or not, but I figured I'd explain it more. The idea here would be to create a little text ui dashboard to run in the chase-car that would show detailed information about the last parse (basically everything that parsed plus maybe some calculations on it). If #12 lands, however, and we have a specialized frontend for viewing data from the chase-car we could probably forgo this and just send everything to the frontend when it's in "chase-car mode." Nevertheless, the idea was something like this:
Except the parse log would probably be reversed (new stuff on top). It would take up the remainder of the screen space. |
This would be great! The change in altitude "Δ alt." could just be called "Ascent rate" or as in aeronautics "Rate of Climb" / "RoC". I don't know if there is a commonly used term for the change in ascent rate but its a good thing to look at too (imho). During our last balloon launch, NBP1, the ascent rate and the change in acent rate was very intersting and telling. The change in ascent rate was linear and sloped down which implys a constant, consistant, slow loss of lift and therefore lifting gas. We didn't realize this until after the flight had ended. I'd love to help, and as always I should learn haskell. This information either on the graphs or on this display would be great! :) |
Another idea to add here is showing the current S-meter reading by making use of hamlib. I'd also like to log that information for later ability to play with data. That said, I'm going to pull the NBP-2 milestone from this, I think there are more pressing things to do for NBP-2, like gpsd integration and CRC (which is mostly done on my end, see #14). This is just a nice-to-have. |
https://github.com/noexc/mapview-cli -- this will eventually make use of either |
Ncurses thing.
The text was updated successfully, but these errors were encountered: