extras issueshttps://gitlab.inria.fr/openvibe/extras/-/issues2024-03-25T16:33:17+01:00https://gitlab.inria.fr/openvibe/extras/-/issues/255Fix share folder for acquisition-server2024-03-25T16:33:17+01:00GARNIER LaurentFix share folder for acquisition-serverGARNIER LaurentGARNIER Laurenthttps://gitlab.inria.fr/openvibe/extras/-/issues/253Port drivers2024-03-19T10:09:28+01:00Thomas PRAMPARTPort drivers- [ ] BioSemiActiveTwo
- [ ] BrainProductsActiCHamp
- [ ] BrainProductsBrainVisionRecorder
- [ ] BrainProductsBrainampSeries
- [ ] BrainProductsVAmp
- [ ] BrainProductsLiveAmp
- [ ] Cognonics
- [ ] CTF/VSM MEG
- [ ] EEGO
- [ ] EGIAmpServ...- [ ] BioSemiActiveTwo
- [ ] BrainProductsActiCHamp
- [ ] BrainProductsBrainVisionRecorder
- [ ] BrainProductsBrainampSeries
- [ ] BrainProductsVAmp
- [ ] BrainProductsLiveAmp
- [ ] Cognonics
- [ ] CTF/VSM MEG
- [ ] EEGO
- [ ] EGIAmpServer
- [ ] Encephalan
- [ ] GTecUSBamp
- [ ] GTecUSBampLegacy
- [ ] GTecUSBampLinux
- [ ] GTecUnicorn
- [ ] GTecGMobilabPlus
- [ ] gNautilusInterface
- [ ] GenericRawFileReader
- [ ] GenericRawTelnetReader
- [x] GenericTimeSignal
- [ ] MBTSmarting
- [ ] MicromedSystemPlusEvolution
- [ ] NeuroServoHid
- [ ] NeuroskyMindset
- [ ] OpenALAudioCapture
- [ ] OpenBCI
- [ ] OpenEEG Modular EEG P2
- [ ] ShimmerGSR
- [ ] SimulatedDeviator
- [ ] TMSiAmplifierPort Acquisition Server to Qt/QMLhttps://gitlab.inria.fr/openvibe/extras/-/issues/252Fix log manager multi lines in acquisition server qt2024-03-06T15:26:55+01:00GARNIER LaurentFix log manager multi lines in acquisition server qtGARNIER LaurentGARNIER Laurenthttps://gitlab.inria.fr/openvibe/extras/-/issues/229Add gitlab-ci2023-12-22T11:13:22+01:00Thomas PRAMPARTAdd gitlab-ciAdd gitlab-ci in order to trigger the gitlab-ci from meta repo.
This will make it easier to test when there is no MR on meta.
documentation: https://docs.gitlab.com/ee/ci/yaml/index.html#triggerprojectAdd gitlab-ci in order to trigger the gitlab-ci from meta repo.
This will make it easier to test when there is no MR on meta.
documentation: https://docs.gitlab.com/ee/ci/yaml/index.html#triggerprojectPort Acquisition Server to Qt/QMLhttps://gitlab.inria.fr/openvibe/extras/-/issues/225Python box memory leak2023-11-09T10:43:30+01:00Thomas PRAMPARTPython box memory leakIssue revealed when sending epochs to a python box even without much processing.
The signal was 4 channels @ 512Hz epoched by 8s every 0.01s.
The data passed from C++ to Python may not be released properly.Issue revealed when sending epochs to a python box even without much processing.
The signal was 4 channels @ 512Hz epoched by 8s every 0.01s.
The data passed from C++ to Python may not be released properly.https://gitlab.inria.fr/openvibe/extras/-/issues/219Update: Uninstall phase2023-10-16T09:35:00+02:00Thomas PRAMPARTUpdate: Uninstall phaseThe uninstall phase from the NSI script for OpenViBE is a bit agressive. It simply removes the whole install directory.
This may lead to accidents when people have omitted "openvibe-x.x.x" subfolder in their custom install and all OpenV...The uninstall phase from the NSI script for OpenViBE is a bit agressive. It simply removes the whole install directory.
This may lead to accidents when people have omitted "openvibe-x.x.x" subfolder in their custom install and all OpenViBE files happen to be next to other things. The uninstall will remove everything!https://gitlab.inria.fr/openvibe/extras/-/issues/215Update: GDF Writer process2023-04-14T16:53:44+02:00Thomas PRAMPARTUpdate: GDF Writer processThe GDF Writer Box writes data in the file as it arrives.
This makes it difficult to fill the header information.
Notably the PHYmin/max and DIGmin/max which are used to scale/offset the data and represent the signal.
It's only possibl...The GDF Writer Box writes data in the file as it arrives.
This makes it difficult to fill the header information.
Notably the PHYmin/max and DIGmin/max which are used to scale/offset the data and represent the signal.
It's only possible to determine their value once all the signal has been received, in order to write all the data with the the resulting scale and offset.
At the moment, since the values are encoded on 8 bytes, which does not really require for scaling/offset, the box's PHYmin/max and DIGmin/max have been hardcoded to the largest floating point and integer possible, generating a scale of 1 and offset of 0.
The generated file is not getting read properly in EEGLab, and it seems to be because of the PHYmin/max and DIGmin/max which are not representative of the signal.https://gitlab.inria.fr/openvibe/extras/-/issues/213Review CSP and XDAWN matrix inversion2023-03-31T11:04:30+02:00Thomas PRAMPARTReview CSP and XDAWN matrix inversionReview how matrix inversions are done in CSP and XDAWN and check if the algorithms are robust to non inversible matrices.
Check if libraries offer different solution than inverting, similar to the "matrix division" in matlab.Review how matrix inversions are done in CSP and XDAWN and check if the algorithms are robust to non inversible matrices.
Check if libraries offer different solution than inverting, similar to the "matrix division" in matlab.https://gitlab.inria.fr/openvibe/extras/-/issues/210update: sklearn trainer train trigger2023-03-17T16:46:42+01:00Thomas PRAMPARTupdate: sklearn trainer train triggerThe Sklearn Train box gets the train trigger from receiving a OVStimulationEnd or OVStreamedMatrixEnd chunk.
The acquisition client does not produce such chunk when the scenario stops.
The generic or gdf stream writers don't add a END ch...The Sklearn Train box gets the train trigger from receiving a OVStimulationEnd or OVStreamedMatrixEnd chunk.
The acquisition client does not produce such chunk when the scenario stops.
The generic or gdf stream writers don't add a END chunk on stop.
The generic and gdf stream readers don't add a END chunk when the data has been fully read.
Only the CSV Writer will produce such chunk at the moment.
Therefore, OpenViBE is not ready to support the use of END chunks to trigger actions.
The easier step would be to change the trigger mechanism of the sklearn trainer box to work like the Classifier trainer box for example.https://gitlab.inria.fr/openvibe/extras/-/issues/208Fix: directx windows installer2023-03-08T18:31:18+01:00Thomas PRAMPARTFix: directx windows installerThe windows installer tries to install directX if its not found on the system (quite rare).
The directX isntallation process is however broken: http://openvibe.inria.fr/tracker/view.php?id=212The windows installer tries to install directX if its not found on the system (quite rare).
The directX isntallation process is however broken: http://openvibe.inria.fr/tracker/view.php?id=212https://gitlab.inria.fr/openvibe/extras/-/issues/206Fix OpenAL dependency2023-03-08T15:32:24+01:00Thomas PRAMPARTFix OpenAL dependencyThe box SoundPlayer depends on the OpenAL library, which needs installing separately.
However it is in the dependencies and OpenAL32.dll appears in the bin directory of the OpenViBE install.
Investigate why it's not picked up and how to...The box SoundPlayer depends on the OpenAL library, which needs installing separately.
However it is in the dependencies and OpenAL32.dll appears in the bin directory of the OpenViBE install.
Investigate why it's not picked up and how to correct it.https://gitlab.inria.fr/openvibe/extras/-/issues/203CI: Ubuntu 20 tests broken2023-02-08T09:51:20+01:00Thomas PRAMPARTCI: Ubuntu 20 tests brokenhttps://gitlab.inria.fr/openvibe/extras/-/issues/197Fix: EDF file closing2023-02-07T16:47:36+01:00Thomas PRAMPARTFix: EDF file closingOccasionally, the EDFFileWriter box fails to close the file, leading to an empty file.Occasionally, the EDFFileWriter box fails to close the file, leading to an empty file.https://gitlab.inria.fr/openvibe/extras/-/issues/102Bug: Acquisition server crash/freeze2022-05-16T17:09:17+02:00DESBOIS ArthurBug: Acquisition server crash/freezeUsing Brain Products BrainAmp HW, we regularly get acquisition problems.
Here's a description of the issue:
- we are using a 64 electrodes setup, and BrainAmp amplifier, plugged in USB to a laptop with Windows 10 & OpenViBE.
- the ACQ ...Using Brain Products BrainAmp HW, we regularly get acquisition problems.
Here's a description of the issue:
- we are using a 64 electrodes setup, and BrainAmp amplifier, plugged in USB to a laptop with Windows 10 & OpenViBE.
- the ACQ server is launched, set to driver *Brain Products BrainAmp Series*. "Connect" & "Play" are pressed. First remark : the "drift" is around 750ms, which seems very high. This displayed metric should be linked to TCP tagging, but is this relevant?
- the designer is launched, and an MI protocol using an ACQ client is run. Signals are correctly transmitted from the ACQ server.
- as long as the scenario is run in the designer, everything is fine.
- Randomly, when the scenario is stopped (with the ACQ server still in "play" mode), we can reach a situation where the ACQ server freezes. One can notice the "drift" value starting to increase erratically, from 750ms to 900, 1000... Sometimes getting back to 750, then going up again, towards 1400-2000. Around 2500, the ACQ server usually freezes.
Obviously, no data can be received by the ACQ client once the ACQ server is frozen. The only solution is to kill the ACQ server, and to launch it again. At that point, the server is usually unstable again (with the drift going around, and eventually freezing), *or* can be stable.
- if the "drift" starts moving erratically, one can "stabilize" the behavior by running a scenario (using the ACQ client) in the designer. Even a simple "ACQ client + plot" can help. Whenever such a scenario is run, the "drift" seems to stabilize, and no freezing/crashing has been observed.
- this behavior was observed on 2 different Windows 10 machines, using the same BrainAmp drivers (as far as we know). One of the two machines has a bug occurrence far larger than the other, but the bug appears on both nonetheless.https://gitlab.inria.fr/openvibe/extras/-/issues/65Update: tcp-tagging forwarding2022-05-16T17:09:22+02:00Thomas PRAMPARTUpdate: tcp-tagging forwardingThe Display Cue Image box forwards to TCP Tagging any stimulation received.
If the box is in a scenario with another box also forwarding to TCP Tagging (e.g. Sound Player), stimulations end up being duplicated as they are sent by both b...The Display Cue Image box forwards to TCP Tagging any stimulation received.
If the box is in a scenario with another box also forwarding to TCP Tagging (e.g. Sound Player), stimulations end up being duplicated as they are sent by both boxes to the the A.S. via TCP Tagging.
Forwarding stimulations on TCP Tagging should be made optional for theses boxes.
A difference could be made for stimulation passing through and those which are actually used by the box.https://gitlab.inria.fr/openvibe/extras/-/issues/10BUG: CI test silent fail2022-05-16T17:09:35+02:00Thomas PRAMPARTBUG: CI test silent failObserved on CI test gdf-readwrite-2.
If the input file for this test does not exist, the scenario cannot work, but the test still passes.
To reproduce:\
ctest -R run_gdf-readwrite-2 => This show test passing
ctest -R run_gdf-read-writ...Observed on CI test gdf-readwrite-2.
If the input file for this test does not exist, the scenario cannot work, but the test still passes.
To reproduce:\
ctest -R run_gdf-readwrite-2 => This show test passing
ctest -R run_gdf-read-write-2 **-V** => This still passes but the verbosity highlights errors.