MRIQC 0.15.0 plugin error



I just recently installed the newest mriqc version, and received this error while running it:

Traceback (most recent call last):
  File "/usr/local/miniconda/bin/mriqc", line 11, in <module>
    load_entry_point('mriqc==0.15.0', 'console_scripts', 'mriqc')()
  File "/usr/local/miniconda/lib/python3.7/site-packages/mriqc/bin/", line 256, in main**plugin_settings)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/", line 599, in run, updatehash=updatehash, config=self.config)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/", line 120, in run
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/", line 248, in _prerun_check
    if np.any(np.array(tasks_mem_gb) > self.memory_gb):
TypeError: '>' not supported between instances of 'numpy.ndarray' and 'str'

My command is:

		unset PYTHONPATH; singularity run $HOME/*mriqc*img 				\
		$data_dir $data_dir/derivatives/mriqc/sub-${s} 					\
		participant 													\
		--participant-label $s 											\
		--write-graph 													\
		--email $email 													\
		--verbose-reports 												\
		--n_proc 8												        \
		--ica 															\
		--hmc-fsl														\
		--fft-spikes-detector 											\
		--fd_thres 0.2											        \
		--mem_gb 30 													\
		--float32 														\
	    --ants-nthreads 2 												\
        --use-plugin $data_dir/mriqc_plugin_${s}.yml 					\	
        -w $data_dir/derivatives/mriqc/sub-${s}

I realize the issue has to do with my plugin, which is:

plugin: LegacyMultiProc
plugin_args: {maxtasksperchild: 1, memory_gb: 30gb, n_procs: 8, raise_insufficient: false}

Removing --use-plugin resolves the problem, but I wanted to see if I’ve improperly named my plugin file or done something else to create this issue, as I’d like to keep the plugin to handle potential memory issues.



I believe it is that gb suffix in the memory_gb value. Removing that should work:

plugin: LegacyMultiProc
plugin_args: {maxtasksperchild: 1, memory_gb: 30, n_procs: 8, raise_insufficient: false}

Yup, that seemed to be the issue, thanks!