The differences in history still exist with today's version of Brainstorm.
If you take the "Remove baseline" entry:
- The first one is coming from the GUI, and the baseline removal is handled directly by the function
in_data.m:
https://github.com/brainstorm-tools/brainstorm3/blob/master/toolbox/io/in_data.m#L407 - The second one was performed from a script, i.e. from
process_baseline.m:
https://github.com/brainstorm-tools/brainstorm3/blob/master/toolbox/process/functions/process_baseline.m#L64
This however indicates that the processing script was not generated using the most optimal option. When generating a pipeline that does successfully import + DC correction + resample: the script generator optimizes the pipeline and adds option entries resample and baseline to the call to the import process.
The epochs are then fully processed and then saved on the drive, instead of being saved by the import process, then read and saved by process_baseline, then read and saved by process_resample.
And you fall back exactly on case #1.
Case #2 is coming from a script that should be fixed.
Example:
The differences you observe in the two graphs could be due to many things. In the first place, the import times for the epoch are not the same. There is a 1 sample shift between the two.
If you can reproduce the same difference between the two options with: a) the same version of Brainstorm and b) the fixed epoch time, there is probably something that should be fixed somewhere.
Let me know how to reproduce and I'll investigate.