I don't know if this is it, but off the top of my head, how exactly did you set up your SUBJECTS_DIR? I assume that you are trying to aggregate stats into a table across a number of subjects after having downloaded the "Structural Extended" packages?
The location of the FS data in the HCP f
Because the surface data in our Cifti files is mapped from the volume using
subject-specific surfaces, it avoids mixing csf and white matter data into
the cortical signal. With a volume parcellation, in order to do something
similar, you would need to parcellate each individual somehow, or have an
You might want to cross-post this to the FreeSurfer list unless there is
someone on the HCP list familiar with qdec, assuming that you've downloaded the
structural extended packages.
Peace,
Matt.
From:
mailto:hcp-users-boun...@humanconnectome.org>>
on behalf of levi solomyak mailto:lsolom...
If you want connectivity matrices based on a parcellation that respects the cortical surface, then you'll need to use the CIFTI data, and you'll need a parcellation to go along with it that is also based on the surfaces (for the cortical grayordinates).
We would definitely suggest that you
Hi Tim,
Thanks for your response. Within the Resting State fMRI 1 preprocessed in
the 500 Subjects + MEG2, I see the rfMRI_REST1_LR.nii.gz, which I presume
is the Nifti-1 data. And then I see an rfMRI_REST1_LR_Atlas.dtseries.nii -
Is that the dtseries.nii Cifti you refer to? Could you explain a b
Hi Everyone,
Thanks a lot for this great discussion! I've learned a lot from it. Sorry
for the delayed response - to clear this up, I'm interested in using
already parcellated functional connectivity matrices. The data Im planning
on using is from the Resting State fMRI 1 preprocessed in the 500
Dear experts,
I've been attempting to generate a stats data table in qdec, but each time
I get a "Index Error: list index is out of range" error. This is occurring
when it is trying to parse the .stats file.
I've made sure that the files all line up exactly with the qdec table and
that SUBJECTS_
As a brief follow-up to this: As you see from Steve's pasted code, the order of the time series in the PTN is based solely on the file name in ConnectomeDB. Importantly, nothing in the REST{1,2}_{LR,RL} naming tells you whether the LR run came first,
or vice-versa. All you know for sure
Ok, but I thought we were talking about correlations here? Another reason for Joelle to be explicit about what she is wanting to do.
--
Michael Harms, Ph.D.
---
Conte Center for the Neuroscience of Mental Disorders
Washington Uni
Hi Michael - for raw covariances - summing covariances is equivalent to temp
concat first.
Cheers
> On 25 Nov 2015, at 17:29, Harms, Michael wrote:
>
>
> To Steve's point and the issue of memory: A critical distinction is whether
> you are intending to work with dense connectomes or parcel
To Steve's point and the issue of memory: A critical distinction is whether you are intending to work with dense connectomes or parcellated connectomes. In the context of parcellated connectomes, both Steve and myself have found a small advantage in
reproducibility if you compute a parcel
11 matches
Mail list logo
