AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

Previous Message Next Message
Message List New Topic Print View
|
rick reynolds
July 19, 2019 09:10AM
Hi,

Two fields that ought to be populated here are slice_code and slice_duration. While slice duration might not be necessary (one could default to TR/nslices), slice code should be set (to provide the slice acquisition order). In some cases the slice_code will not have a possible value to correspond with the slice order (NIFTI cannot support arbitrary slice timing). What was the slice timing in this case? Was this a multi-band acquisition?

If you know the slice timing, it is possible to pass it separately, which would allow for a timing that NIFTI cannot represent.

- rick
Reply Quote
RSS
Subject Author Posted

3dinfo and slice timing

ns July 16, 2019 05:53PM

Re: 3dinfo and slice timing

rick reynolds July 16, 2019 06:52PM

Re: 3dinfo and slice timing

ns July 16, 2019 10:31PM

Re: 3dinfo and slice timing

rick reynolds July 16, 2019 11:00PM

Re: 3dinfo and slice timing

ns July 17, 2019 09:58AM

Re: 3dinfo and slice timing

rick reynolds July 19, 2019 09:10AM