Closed mpompolas closed 2 years ago
Each trial's history is logged on the config.json
file.
It can be transferred to a different file at some point in order not to have too much information on the config file.
NOTE: It is up to the user to follow the preprocessing steps that were applied on the training dataset. Preprocessing is not automated
There are two levels of signal datasets in Brainstorm:
The first one, as the name suggests, is just a link to the raw file that is created by the acquisition system. There are no preprocessing steps on it. This link to the raw file has access to the entire duration of the recording.
Trials on the other hand, are specific segments in time of the recording. They are typically chosen around timings of interest (e.g. like a stimulus presentation). The trials can be created just by chopping the raw recording, or they can be created after the raw files have undergone preprocessing steps (artifact removal, filtering, resampling etc.) Typically, all trials should undergo preprocessing.
Ivadomed training: The training of the Ivadomed model is being done on the trials level. So the preprocessing is already done.
When we have a trained model and we want to segment a new trial, it makes sense that the trials have to undergo the same preprocessing steps for the model to work.
For segmentation of the raw files, since a sliding window is creating new "trials", the same preprocessing needs to be applied.
Sugesstion For all this to work seamlessly with ivadomed, all preprocessing steps will be logged to the config file and then applied to the newly created "trials" that the NIFTIs are based on.
I am already doing something similar by logging the trials filenames, sampling rate of the trials, and the Brainstorm parameters used on the
process_ivadomed_create_dataset.m
function.Check: