-
Notifications
You must be signed in to change notification settings - Fork 12
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
[enh] Make all process compatible with raw files #219
Conversation
Done 👍
If there are cases where only processing happens, the process could be written as Category
|
Thank you for the comment. The file are now registered in the database. However, i am not able to open it
it seems that the file is created but matlab cannot open it |
@rcassani When using the filter type of process, is there an easy way to have access to the events (so we could remove those lines https://github.com/Nirstorm/nirstorm/pull/219/files#diff-1ab9716e183e1a953da0f256a555bfac4adad214f253515ee0e3c0534b9ad0d9L106-L113) and not to have to load the entire file a second time? |
Unfortunately, it is necessary to read the events from the file. It can be faster by reading only that field for imported data:
For raw files it should be fast to read |
Thank you. it seems that we can make minimal change to bst_process to have the event. would that be ok for you ? (see brainstorm-tools/brainstorm3#655)
Do you have any idea about that issue? Edit: it seems to be working :) |
List of processes to adapt for continuous recording: Preprocessing
MBLL
Global
|
Hi @Edouard2laire, is my input already required for this PR? |
Hello, I think this is ready to be merged. Let me know if you want to review it or if I should merge it as is. One issue I would like us to check is brainstorm-tools/brainstorm3#656 as it is often important in nirs to check what the preprocessing steps are doing to the data so we would open the raw data and after motion correction to be sure the motion correction step worked well and it makes it necessary to have two continuous files open at the same time. |
Compiled by Zhengchen Cai
Accidentally closed the PR. Reopening here #223 |
This PAr aims at improving the way files are handled. The objective is to keep the type of the files. So if the input is raw, the output is raw. If the input is epoched data, so is the output.
@rcassani, could you check what i am doing wrong? the output file is not registered to the database when creating a new raw file?
it would be nice if it was simpler from the API point of view to save/load either epoch data or raw files as from the process point of view, we don't really care if the file we are processing is raw or epoch. Currently, it leads to a lot of code duplication and case handling to make sure each process can work on either raw or epoched data...