Open psadil opened 10 months ago
It looks like the IQMs are not submitted to MRIQC's metrics repository when the --fft-spikes-detector is turned on, and that this is due to a mismatched schema.
--fft-spikes-detector
(Sorry if this is not the right repo for this issue.)
singularity run --bind $PWD docker://nipreps/mriqc:23.1.0 -w $PWD/work --notrack --fd_thres 0.3 --nprocs 2 --mem 16000 rawdata derivatives participant
23.1.0
Singularity
Yes
No
INFO: Using cached SIF image 240111-18:31:30,462 cli IMPORTANT: Running MRIQC version 23.1.0: * BIDS dataset path: /fastscratch/myscratch/pssadil/mriqc/rawdata. * Output folder: /fastscratch/myscratch/pssadil/mriqc/derivatives3. * Analysis levels: ['participant']. 240111-18:31:41,346 cli WARNING: IMPORTANT: Anonymized quality metrics (IQMs) will be submitted to MRIQC's metrics repository. Submission of IQMs can be disabled using the ``--no-sub`` argument. Please visit https://mriqc.readthedocs.io/en/latest/dsa.html to revise MRIQC's Data Sharing Agreement. 240111-18:32:11,719 nipype.interface WARNING: QC metrics upload failed to create an ID for the record uplOADED. rEsponse from server follows: {"_status": "ERR", "_issues": {"spikes_num": "unknown field"}, "_error": {"code": 422, "message": "Insertion failure: 1 document(s) contain(s) error(s)"}} 240111-18:32:11,720 nipype.interface WARNING: QC metrics failed to upload. Status 422: {"_status": "ERR", "_issues": {"spikes_num": "unknown field"}, "_error": {"code": 422, "message": "Insertion failure: 1 document(s) contain(s) error(s)"}} 240111-18:32:15,531 cli WARNING: IMPORTANT: Anonymized quality metrics (IQMs) will be submitted to MRIQC's metrics repository. Submission of IQMs can be disabled using the ``--no-sub`` argument. Please visit https://mriqc.readthedocs.io/en/latest/dsa.html to revise MRIQC's Data Sharing Agreement. 240111-18:32:15,912 cli IMPORTANT: Participant level finished successfully.
No response
Thanks for noticing this!
What happened?
It looks like the IQMs are not submitted to MRIQC's metrics repository when the
--fft-spikes-detector
is turned on, and that this is due to a mismatched schema.(Sorry if this is not the right repo for this issue.)
What command did you use?
What version of the software are you running?
23.1.0
How are you running this software?
Singularity
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