Skip to content
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

Open
MatzElectronics opened this issue Sep 17, 2016 · 9 comments
Open

File output of recorded sensor data #31

MatzElectronics opened this issue Sep 17, 2016 · 9 comments

Comments

@MatzElectronics
Copy link
Collaborator

Preferably as a .csv format file with the first line being the column headers.

@JasonDorie
Copy link
Collaborator

Completed, in ActiveDevelopment branch

@jrleeman
Copy link

Is there an automated build of the ActiveDev branch? I'd like to use/test this functionality.

@JasonDorie
Copy link
Collaborator

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:

Is there an automated build of the ActiveDev branch? I'd like to use/test
this functionality.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANak_iOAiWo8pDusKqH3d06WpLbEGylqks5q0hrsgaJpZM4J_i7c
.

@jrleeman
Copy link

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?

@JasonDorie
Copy link
Collaborator

Kind of, but I don't actually know in GroundStation when it's "flying". I
could stream to disk when the motors are spinning, but if you disarm /
rearm and fly again, do I append, overwrite, or increment to a new file?
What would your preference be?

J

On Tuesday, October 18, 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?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANak_tFVji_rGc1MKg1_AfNiN0qfE92hks5q1XsZgaJpZM4J_i7c
.

@jrleeman
Copy link

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?

@MatzElectronics
Copy link
Collaborator Author

MatzElectronics commented Oct 19, 2016 via email

@jrleeman
Copy link

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)

@MatzElectronics
Copy link
Collaborator Author

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.

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

No branches or pull requests

3 participants