Hello Francois,
I found a bug with the "copy to other folders" function for Noise Covariance files.
I am processing hyperscanned EEG files. I am planning to run source level analyses so I have imported the raw data files in duplicate, then modified the channel file so that only the channels corresponding to the subject of interest get processed downstream.
Everything works fine in my pipeline, except when I try and use the aforementioned function to copy the Noise Covariance files to my epoched file folder. I cannot correctly copy the file even when using Brainstorm's copy paste functions. The copied file shows a covariance matrix with a single square (where is should have 64, or 96, etc).
An interesting caveat of this problem is that it only occurs when the file corresponds to the second or third subject in the raw data file (i.e. not the first 32 channels).
I caught the problem because source estimation threw an error. I have managed to bypass this problem by copy/pasting the file directly within MATLAB or Windows Explorer. It then correctly copies the file, and source estimation proceeds without issue.
I think not too many people are doing hyperscanning yet... but I thought this strange issue was something worth mentioning to you.
Cheers,
Jared
P.S. Actually, it is a problem for all files, regardless of subject. It is just that the nature of the problem changes. When the subject is the first in the data set (e.g. first 32 channels), the copied Noise Covariance matrix is inverted and duplicated on the second set of channels. However, because a correct covariance matrix exists for the channels of interest, source estimation proceeds without problem, despite the copy error.
The copy of the noise covariance matrix doesn't simply do a copy-paste of the file, it also re-arranges the rows and columns of the covariance matrix based on the names of the channels in the source and destination channel names.
If you modified or reorganized these files yourself, it might confuse completely this algorithm.
I don't think it will be possible for me to reproduce on my end what you describe because it involves manual modifications, so I won't be able to debug it. And this is maybe an issue that is too specific to be addressed in the general distribution of Brainstorm.
If you can identify precise and reproducible cases in which you have not modified any channel file or data file, and you still get weird behaviors of this menu "copy to other folders", please describe precisely how to reproduce the issue and include some screen captures to illustrate the problem.