Generic Raw Telnet Reader - Format of Raw Buffer
Posted: Mon Feb 16, 2015 10:35 pm
I am trying to send an EEG stream over the acquisition server through the 'Generic Raw Telnet Reader'
My python servero sends 14 channels of data on one line.
(i modified the acquisition ui to accept my 1 line sample count)
My question is, what format should this be sent in?
I was told in binary, but should there be a delimiter in between data pieces? (ie 0x00)
or is it one complete chunk of binary that is read in segments determined by 'sample type'
that allows you to select the type of byte. (integer, float, etc)
The documentation for the OVTK_NodeId_Buffer_StreamedMatrix_RawBuffer says 'array of float64'
when sending an array from python, i believe it is delimited by an 0x00 byte, i was curious if the array
is in an EBML format, or can i just send it directly?
my client only sends the raw eeg data line by line, i was wondering if i needed header or supply more
details, or if i could get away with the bare minimum, as it seems to be displaying the data properly.
I've been using ebml spy to view the messages and the sample type indicates "float 64"
i remember reading that though it receives other data types, that openvibe converts to
a float64 format to maintain higher precision, but that its only localy. So my question on
this, is if I the acquisition server is reading 32-bit data is the result going to 'display' a
32-bit result, or is the displayed result actually a 64-bit float.
i just wanted to be sure, because I wanted to verify what i was sending with what it is receiving,
and when it seems that its displaying the data correctly in the visualizations, the ebml spy indicates
its receiving floats.
my data format is in the range of -8900 to 8900, i was wondering if I needed to scale this down as well,
or will openvibe scale it down on its own?
My python servero sends 14 channels of data on one line.
(i modified the acquisition ui to accept my 1 line sample count)
My question is, what format should this be sent in?
I was told in binary, but should there be a delimiter in between data pieces? (ie 0x00)
or is it one complete chunk of binary that is read in segments determined by 'sample type'
that allows you to select the type of byte. (integer, float, etc)
The documentation for the OVTK_NodeId_Buffer_StreamedMatrix_RawBuffer says 'array of float64'
when sending an array from python, i believe it is delimited by an 0x00 byte, i was curious if the array
is in an EBML format, or can i just send it directly?
my client only sends the raw eeg data line by line, i was wondering if i needed header or supply more
details, or if i could get away with the bare minimum, as it seems to be displaying the data properly.
I've been using ebml spy to view the messages and the sample type indicates "float 64"
i remember reading that though it receives other data types, that openvibe converts to
a float64 format to maintain higher precision, but that its only localy. So my question on
this, is if I the acquisition server is reading 32-bit data is the result going to 'display' a
32-bit result, or is the displayed result actually a 64-bit float.
i just wanted to be sure, because I wanted to verify what i was sending with what it is receiving,
and when it seems that its displaying the data correctly in the visualizations, the ebml spy indicates
its receiving floats.
my data format is in the range of -8900 to 8900, i was wondering if I needed to scale this down as well,
or will openvibe scale it down on its own?