-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gui graphs #371
base: gui
Are you sure you want to change the base?
Gui graphs #371
Conversation
Fix sessionStore streamParameter set Clean up backend
@SamedVossberg In the
What was the motivation behind that? I guess something related to the example test run? I removed it now so that the LSL Stream can be tested in the frontend |
@timonmerk The idea was to have a timeout for the lsl stream to terminate if no new data was incoming. As back then there was no option to stop the stream manually (we tried with a keyboard interrupt first back then but then decided against it) the timeout terminated the lsl connection if there wasn't any new data incoming for three consecutive seconds. And yes, it can be deleted as with the frontend established this will be deprecated. |
…layout, debugging socket
@SamedVossberg I updated now the files that the full spectrums are returned in the features. Unfortunately though there is a bug in the settings that I am not able to fix, as mentioned here: #377 (comment) @toni-neurosc it would be great if you could have a look how we could find a simple solution how to fix this bug. I tried to remove all the Also, regarding the issue there we exceed the number of columns in the SQL database, I would suggest for now to limit the number of channels, in this way the feature number doesn't exceed the 2000 sqlite limit. Not a nice solution.. but something that allows us to keep developing at the moment. |
…o prevent Vite from running out of memory during build
@SamedVossberg I've created this PR so some changes can be discussed