Timeline for Data format for binary data transfer
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 13, 2015 at 3:36 | comment | added | heltonbiker | Edf is just mentioned as a starting point, of course its useful ideas can be applied without its rather artificial limitations. @jbcolmenares, anything that changes between consecutive frames should be encoded in each frame, I think, so I would suggest you to create a field in your frame to describe sensor configuration for that frame. Alternatively, you could have something like segments, that is, you have a handshake, then write the start of a segment (with some parameters, then a datastream, then an end-of-segment marker, then another start of segment... | |
| May 12, 2015 at 20:30 | comment | added | whatsisname | EDF is pretty miserable, because of it's limits on record sizes and others. Reasonable for 1992, not so much now. However, it's a reasonable example to look at as a starting point. | |
| May 12, 2015 at 20:14 | comment | added | cauchi | what if the number of channels change? in my case it could happen. It would be the equivalent of connecting another signal to the probe. You redo the handshake? | |
| May 12, 2015 at 19:31 | comment | added | heltonbiker | The idea would not stream the header, but only use its content for "handshaking" between oscilloscope and probe before streaming starts. Then, when you stream, you stream only the raw part, composed of a sequence of frames, each frame containing the appropriate amount of samples from each probe. | |
| May 12, 2015 at 18:51 | comment | added | cauchi | The header is way too big for streaming data in an oscilloscope. The EDF looks like the SEG data formats used in geophysics. Had you heard of the TLV stream data format that @shawty talks about? looks simply and easy to implement. | |
| May 12, 2015 at 17:12 | history | answered | heltonbiker | CC BY-SA 3.0 |