Has the availableRAM_GB option been removed or replaced? about clean_rawdata HOT 7 CLOSED

Dear Cyrille,

Which version were you using before? Probably a very old version. There were updates to clean_rawdata that had conflicts, so this option was removed because of that about a year ago. Who told you to use that option? Copying @MakotoMiyakoshi here.

Arno

from clean_rawdata.

Hello! I have the same question as Cyrille.

" 'availableRAM_GB' is for clean_rawdata1.10. For any newer version, it will cause error. "

Using the same parameters, the final results from clean_rawdata() fluctuate after ASR. It is demonstrated that adding availableRAM_GB fixes this (in the link below), but now we can't use it if we are using the newer version of clean_rawdata?

https://sccn.ucsd.edu/wiki/Artifact_Subspace_Reconstruction_(ASR)

Is there any way fix to this? This is a huge problem for replicability. Any help would be much appreciated.

Thank you!
Armen

from clean_rawdata.

Could you try resetting the random seed before calling the function. Also better call cleanArtifact directly which has more options.

We will try to add back the option. @MakotoMiyakoshi maybe you could help?

from clean_rawdata.

from clean_rawdata.

from clean_rawdata.

Thanks Arnaud! I believe this is working. But it's hard to tell because first I am removing bad channels using clean_rawdata and it is also giving me inconsistent results. I ran the same file 10 times through clean_rawdata. Sometimes it says there are 3 bad channels, sometimes 4, sometimes 5. Is there a similar fix that can deliver reproducible results for the other functions in clean_rawdata such as removing bad channels? And then I'm assuming this may be a problem for the additional removal of bad data periods function?

from clean_rawdata.

Now closing this report. I have added back availableRAM_GB but not 100% it works as before.

from clean_rawdata.