mriqc
mriqc copied to clipboard
zero-filled frame detector false alarm?
dataset: https://openneuro.org/datasets/ds001037/versions/00001 report: https://s3.amazonaws.com/openneuro.outputs/1361b7bb7d60eddbf8c9595bc6f9ef6f/5dd8e547-44ca-47df-94b0-479b6ea7eeaa/reports/sub-CG_T1w.html
Don't see evidence of rotatation or zero filled frame
I'll check locally on that subject. With --verbose-reports
it should be possible to see what is detected as frame.
Just to +1 this... I too am getting "Detected a zero-filled frame, has the original image been rotated?" but there's no apparent rotation, no blank slices.
Mriqc is probably getting confused by the blank from defacing. Is that possible?
On Feb 14, 2018 05:10, "Thomas Nichols" [email protected] wrote:
Just to +1 this... I too am getting "Detected a zero-filled frame, has the original image been rotated?" but there's no apparent rotation, no blank slices.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/poldracklab/mriqc/issues/637#issuecomment-365602114, or mute the thread https://github.com/notifications/unsubscribe-auth/AAkhxiSk2g0ubYWSCFl05xe8Em8l79f3ks5tUtrtgaJpZM4PD5ka .
Don't think so. I'm running this on Nifti data fresh from DICOM conversion. I can send the dataset if you want.
That'd be sweet
On Feb 14, 2018 10:56, "Thomas Nichols" [email protected] wrote:
Don't think so. I'm running this on Nifti data fresh from DICOM conversion. I can send the dataset if you want.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/poldracklab/mriqc/issues/637#issuecomment-365708765, or mute the thread https://github.com/notifications/unsubscribe-auth/AAkhxgSvvcOQce_QsX4CmNoXOp65WDcgks5tUyx5gaJpZM4PD5ka .
Here you go! https://www.dropbox.com/s/z32s2p2t1v3f96x/ForOscar.zip?dl=0 (will finish uploading on my pokey ADSL line in 30 min)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Another +1 here. I also got the same warning for some data that I recently processed with mriqc. Have you ever found out what was the reason for this warning and what to do about it?
Same here, the visual report looks fine and I cannot see any evidence for rotation nor blank slices..
I have the same issue, I am however using defaced T1 images.
Same here. It appears repeatedly. Have the MRIQC team has a solution or update on it? Maybe we should simply label files with such error as 'good' in postprocessing?
Duplicate of #1035.
As of 23.1.0 this has been disabled, hoping for a more selective detector to be implemented.