mriqc: pybids recent changes break compatibility: "No scans were found"

Hello,

I have been able to run mriqc on a workstation. I then moved on to install a copy on our server and I think I have followed the same steps. When I run mriqc /run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001 /run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001_output/ participant --participant_label sub-01 sub-02 -w /run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001_work/

I get the following error

/home/MBIAL/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/sklearn/cross_validation.py:44: DeprecationWarning: This module was deprecated in version 0.18 in favor of the model_selection module into which all the refactored classes and functions are moved. Also note that the interface of the new CV iterators are different from that of this module. This module will be removed in 0.20. “This module will be removed in 0.20.”, DeprecationWarning) 170124-23:15:25,490 mriqc INFO: Running MRIQC-0.9.0-rc1 (analysis_level=participant, participant_label=[‘sub-01’, ‘sub-02’]) Settings={u’report_dir’: u’/run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001_output/reports’, u’work_dir’: ‘/run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001_work’, u’n_procs’: 5, u’bids_dir’: ‘/run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001’, u’hmc_afni’: False, u’write_graph’: False, u’ants_nthreads’: 6, u’verbose_reports’: False, u’testing’: False, u’output_dir’: ‘/run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001_output’} 170124-23:15:25,509 mriqc WARNING: No anatomical scans were found in /run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001 170124-23:15:25,509 mriqc WARNING: No functional scans were found in /run/media/MBIAL/MBIAL_STORAGE/Parekh/ds001

This is the BIDS example dataset that I am trying to run. I have successfully been able to run the same on the test workstation (and other dataset) but none of them seem to be running on the server (same error message). Any suggestions would be greatly appreciated. I have also tried moving the dataset to the server directly (instead of using a storage device) but the above issue persists.

Interestingly, I can use the workstation to process the same location of data! The test workstation and the server are both running Redhat.

Thanks and Regards Pravesh