Open Tordelap opened 1 year ago
The interface says it was killed. How much memory do you have available?
I am working on a Ubuntu/Linux docker. I have understood that I cannot set a memory limit in this case.
My system has 32 GB RAM memory and 12th Gen Intel® Core™ i9-12900 × 24
I cannot set a memory limit in this case.
I'm not sure what you mean by that. But you should have enough memory. It could be a fluke, and you can just try rerunning. If you still have your working directory, it will try to pick up where it left off.
Thank you Chris,
Sorry, I meant that on Ubuntu, apparently, Docker can use all available host memory (32GB in my case) and I have double check this already. I do not think one single subject is using all that memory, right? I am currently running another subject and I will try to re-run the first one as you recommended.
Hi,
After trying to re-run the same subject I've got this error:
fmriprep-docker --fs-license-file /media/usuari/Datos/freesurfer/license.txt /media/usuari/Datos/MBCT_OCD /media/usuari/Datos/MBCT_OCD/out -w /media/usuari/Datos/trash --participant-label sub-050100101B --use-aroma --output-spaces MNI152NLin2009cAsym
RUNNING: docker run --rm -e DOCKER_VERSION_8395080871=20.10.17 -it -v /media/usuari/Datos/freesurfer/license.txt:/opt/freesurfer/license.txt:ro -v /media/usuari/Datos/MBCT_OCD:/data:ro -v /media/usuari/Datos/MBCT_OCD/out:/out -v /media/usuari/Datos/trash:/scratch nipreps/fmriprep:22.0.2 /data /out participant --participant-label sub-050100101B --use-aroma -w /scratch --output-spaces MNI152NLin2009cAsym
You are using fMRIPrep-22.0.2, and a newer version of fMRIPrep is available: 22.1.0.
Please check out our documentation about how and when to upgrade:
https://fmriprep.readthedocs.io/en/latest/faq.html#upgrading
Traceback (most recent call last):
File "/opt/conda/bin/fmriprep", line 8, in
fmriprep-docker /media/usuari/Datos/MBCT_OCD /media/usuari/Datos/MBCT_OCD/out
You're nesting your outputs in your inputs. That's bound to cause problems.
Thank you Chris, I will correct this. Also, my internal disk died and that might be the reason of the memory problems and other errors. Maybe it was a hardware problem after all.
Hello Chris,
I have re-run the same participant and it ended successfully, it was indeed a memory problem. I am getting this warning for every subject:
nipype.workflow WARNING: Some nodes exceed the total amount of memory available (27.99GB)
Should I use a --low-mem flag or a --mem-mb 26000 for the remaining sample? What is the best approach? Or should I erase the first participant and run the whole sample with the same flag? Does this flags affect the preprocessing pipeline (any step) or just increase preprocessing times?
Another possible approach, but a less comfortable one, is to re-run every time a participant's process is killed...
Thank you very much in advance,
Víctor.
The --low-mem
flag does very little anymore. If you are using ICA-AROMA it will have an impact; otherwise we've been able to reduce the memory consumption of the other nodes that we targeted. The main impact is that some files that would have been compressed will be uncompressed to allow for memory mapping, so the cost is disk space, not time.
--mem-mb
will only change how much memory fMRIPrep thinks is available, which won't change some nodes exceeding 28GB.
Another possible approach, but a less comfortable one, is to re-run every time a participant's process is killed...
Agreed that it's not ideal, but memory crashes are hard to eliminate completely for such a large workflow. If you can keep the same working directory around, then it should not be too onerous. You could even try to auto-retry:
for TRY in 1 2 3; do
fmriprep-docker ... && break
done
Thank you very much Chris for your detailed response, I guess I can keep the same working directory and I will try auto-retry!
What happened?
Hello,
I was trying to preprocess a first subject within a simple data set that just includes T1 and resting state images. I ran the first subject and it reported an error that I do not quite understand. I have had other problems with the BIDS validation and .json files with this sample, but I think I have solved them. Am I doing something wrong? Can you help me please?
Thank you very much!
What command did you use?
What version of fMRIPrep are you running?
fmriprep-docker-22.0.2
How are you running fMRIPrep?
Docker
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
Additional information / screenshots
No response