-
Notifications
You must be signed in to change notification settings - Fork 12
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
update DB with correct image info #26
Comments
ghost
assigned rfdougherty
Jan 17, 2013
kevlarkevin
added a commit
that referenced
this issue
Dec 16, 2014
processor checks size, mm_per_vox, num_slices, num_timepoints, and duration after parse, and updates the Epoch info in the DB. |
kevlarkevin
added a commit
that referenced
this issue
Jan 5, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a user stops a scan prematurely, the actual number of timepoints will differ from the prescribed number. We should update Epoch.num_timepoints and Epoch.duration to reflect the actual values. (Epoch.prescribed_duration will remain unchanged.)
For mux (multiband) scans, the number of slices is currently computed correctly from the header, but we should allow for the fact that it might need to be updated after the recon is done. So we should update Epoch.num_slices as well.
Both of these can be updated after the NIFTI is generated. Modify dicomutil.DicomAcquisition.convert and pfile.PFile.to_nii to return the actual num_timepoints and num_slices, and the relevant processor pipelines should be modified to push this info to the Epoch.
The text was updated successfully, but these errors were encountered: