Scenario processing and clock time
Posted: Fri Dec 06, 2019 12:58 pm
We designed our own BCI scenario with 2 acquisition clients, some parallel epoch power calculations of different frequency bands (pipeline of temporal filter, time based epoching, simple DSP, signal average, epoch average; as seen in the neurofeedback BCI example). Additionally, we programmed our own boxes to send stimulations.
We wondered how long it takes OpenViBE to process all the input from the acquisition server to reach the last box? In our case, the last box would be a file writer. Does the real-time imply that all the input chunk is finished processing through all the boxes within the scenario before the next input chunk enters the first box after the acquisition client?
Am I correct in the assumption, that the chunk that enters OpenViBE always keeps the same chunk input time when it is processed through all the boxes in series? Additionally, is there a way that in stimulations, the "real" time (a clock-time) when the stimulation was generated is saved and not the chunk input time?
Thanks a lot for your help.
We wondered how long it takes OpenViBE to process all the input from the acquisition server to reach the last box? In our case, the last box would be a file writer. Does the real-time imply that all the input chunk is finished processing through all the boxes within the scenario before the next input chunk enters the first box after the acquisition client?
Am I correct in the assumption, that the chunk that enters OpenViBE always keeps the same chunk input time when it is processed through all the boxes in series? Additionally, is there a way that in stimulations, the "real" time (a clock-time) when the stimulation was generated is saved and not the chunk input time?
Thanks a lot for your help.