-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File output of recorded sensor data #31
Comments
Completed, in ActiveDevelopment branch |
Is there an automated build of the ActiveDev branch? I'd like to use/test this functionality. |
There isn't, no. I disabled the auto-build we had because it kept failing. On Sunday, October 16, 2016, John Leeman [email protected] wrote:
|
I did play with this before I borked my setup. Any way to make this a checkbox instead of a menu option. i.e. you could "enable logging" and stream to a file during the entire flight? |
Kind of, but I don't actually know in GroundStation when it's "flying". I J On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
I'd be okay if it logged the entire time the box is checked - flying or not. Maybe that's just me. What about naming the files with a timestamp like DDMMYY-HHMMSS.csv or something similar? |
I like the idea of a datestamp filename if it's not too much trouble - I
would recommend YYYY-MM-DD_HH-MM-SS.csv. Longer, but then when you sort
the files alphabetically, it also sorts them in date order.
|
That could work. What about adopting the naming convention used on seismograms and other geophysical data? YYYY-MM-DDTHH:MM:SS (i.e. 2016-09-03T12:02:22) |
Functionality is tested and verified. Will leave open for two pieces: Some reference to time (cycle, phase, anything that time can be inferred from), and default file naming if possible. If it's not possible or easy to do, we can skip that part because the user has the ability to name the file themselves. |
Preferably as a .csv format file with the first line being the column headers.
The text was updated successfully, but these errors were encountered: