n.edu>>
> Cc: "hcp-users@humanconnectome.org <mailto:hcp-users@humanconnectome.org>"
> <hcp-users@humanconnectome.org <mailto:hcp-users@humanconnectome.org>>
> Subject: Re: [HCP-Users] Negative Voxel Values signed int 16 vs uint16 issue
>
> NiFTI-1.1 doe
hcp-users-boun...@humanconnectome.org> on behalf of Timothy Coalson <tsc...@mst.edu>
Date: Thursday, March 3, 2016 at 3:14 PM
To: "Garrett T. McGrath" <gmcgr...@princeton.edu>
Cc: "hcp-users@humanconnectome.org" <hcp-users@humanconnectome.org>
Subject: Re: [HC
NiFTI-1.1 does in fact support both signed and unsigned int16:
#define DT_INT16 4
...
#define DT_UINT16512 /* unsigned short (16 bits) */
I don't know if this was the case in NiFTI-1.0, but NiFTI-1.1 has been
around so long it would be strange if tools
Hi,
We’ve been going with FLOAT32 in our conversions, which I believe is the
default behavior of ‘dcm2nii’.
cheers,
-MH
--
Michael Harms, Ph.D.
---
Conte Center for the Neuroscience of Mental Disorders
Washington University School of
We've had a set of users that have discovered an issue with their latest
datasets that I'm hoping there might be a best practice for dealing with in
regards to FSL.
I've received some specific context from the end users on what they are
capturing:
Users are collecting single-band spin echo EPI
