Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

n-jobs in generic-prep function #100

Open
TheUwe opened this issue Jul 25, 2019 · 2 comments
Open

n-jobs in generic-prep function #100

TheUwe opened this issue Jul 25, 2019 · 2 comments

Comments

@TheUwe
Copy link

TheUwe commented Jul 25, 2019

While pre-processing resting state fMRI data, I tried to limit the processing done in parallel, since my cluster allows only for a limited amount of capacity used. Therefore, I wanted to use the implemented parameter '--n-jobs' of the 'generic-prep' function. Unfortunately, I couldn't manage to let the parameter be accepted.

I tried my basic code
SAMRI generic-prep -n-jobs 4 -o Exp1 -f '{"acquisition":["rsfMRI"],"subject":["169"]}' -s '{"acquisition":["FLASH"],"subject":["169"]}' Exp1/bids samriTemplates/dsurqec_200micron.nii
with various other options of -n-jobs that all led to the following error:
SAMRI: error: unrecognized arguments: -n-jobs samriTemplates/dsurqec_200micron.nii

Running this code without the n-jobs parameter leads to an error message:

Message from root@eu-login-10-ng on pts/2 at 10:40 ...
You are overloading this login node (2 threads N4BiasFieldCorr +
9 threads SAMRI + 1 thread python on 4 CPUS).
Please DO NOT use more than 4 threads + processes on login nodes !
Please use LSF, if you need more resources.

@TheChymera
Copy link
Member

TheChymera commented Jul 26, 2019

Thank you for the report.
I have reviewed the code and it should work. Please specify:

  • The exact command which you used (the command you posted above does not specify a jobs number)
  • How you know that this used “too many cores” --- ideally while specifying the number of cores.

@TheChymera
Copy link
Member

@TheUwe is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants