Skip to content
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

Closed
rfdougherty opened this issue Jan 17, 2013 · 1 comment
Closed

update DB with correct image info #26

rfdougherty opened this issue Jan 17, 2013 · 1 comment
Assignees

Comments

@rfdougherty
Copy link
Member

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.

@ghost ghost assigned rfdougherty Jan 17, 2013
@gsfr gsfr assigned Minda and gsfr Feb 4, 2014
@gsfr gsfr assigned rfdougherty and unassigned gsfr Feb 11, 2014
kevlarkevin added a commit that referenced this issue Dec 16, 2014
@kevlarkevin
Copy link
Contributor

processor checks size, mm_per_vox, num_slices, num_timepoints, and duration after parse, and updates the Epoch info in the DB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants