You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the LSL networking protocol to send the AvgBandPower, the data output is only one single value.
Expected
Like for the other protocol, the expected output should be the 5 avg power value (one per band).
In the W_Networking.pde/sendNormalizedPowerBandData function, the loop across each frequency band is missing for the LSL case.
Operating System and Version
Windows
GUI Version
5.1.0
Running standalone app
downloaded app
Type of OpenBCI Board
Synthetic
Are you using a WiFi Shield?
No
Console Log
Thank you!
The text was updated successfully, but these errors were encountered:
Confirmed using Networking test kit. When this metric was added it was in support of OpenBCI team using UDP. Thanks for bringing this oversight to our attention. We will include the fix in the next version of the GUI.
Actually the code in sendNormalizedPowerBandData() is fine, since we pass in a single dimension array, which is a valid option for LSL push_sample. What's wrong is the number of channels per sample, which should be 5 instead of 1.
In the screenshot, you'll see that this is now correct with 5 band powers whose sum is 1. The sampling rate is roughly equal to the framerate of the GUI (since that's when updates occur for a derivative metric).
Getting a PR for this in now since it's such an easy fix.
Problem
When using the LSL networking protocol to send the AvgBandPower, the data output is only one single value.
Expected
Like for the other protocol, the expected output should be the 5 avg power value (one per band).
In the W_Networking.pde/sendNormalizedPowerBandData function, the loop across each frequency band is missing for the LSL case.
Operating System and Version
Windows
GUI Version
5.1.0
Running standalone app
downloaded app
Type of OpenBCI Board
Synthetic
Are you using a WiFi Shield?
No
Console Log
Thank you!
The text was updated successfully, but these errors were encountered: