Skip to content
This repository has been archived by the owner on Dec 14, 2022. It is now read-only.

Be able to step through historical data #13

Open
relrod opened this issue Dec 3, 2014 · 2 comments
Open

Be able to step through historical data #13

relrod opened this issue Dec 3, 2014 · 2 comments

Comments

@relrod
Copy link
Member

relrod commented Dec 3, 2014

...to replay the track.

@relrod relrod added this to the v2.1 milestone Dec 20, 2014
@relrod
Copy link
Member Author

relrod commented Dec 20, 2014

Some thoughts:

Several people (@kd8jkf, @phuzion) asked for this after the last launch.

Probably the simplest thing to do here is to assign each packet a number and store that in a JSON file, then let a client request a particular packet number (probably with a pretty UI to do this for you). Parse the file, pick the entry with the requested packet id, and send it back to the client.

We'll have to decide what the frontend side of this should all look like. Mostly: Do we want to allow stepping back during an ongoing balloon launch, or should it be a separate endpoint? I kind of think from a UI/UX perspective, the latter would be best (otherwise what happens if we receive a new packet while you are stepped back? And what happens if you forget to step all the way forward again? Etc.)

I'm assigning this to 2.1, but I don't expect 2.1 to land until sometime after NBP-2 happens.

@kg4sgp
Copy link

kg4sgp commented Dec 20, 2014

I dont think its really needed for an ongoing balloon launch. It should be a separate endpoint imo. Speaking of packet numbers, that might be a good idea in general for the HAB telemetry its self, but thats a discussion for another thread.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants