You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I think this may be a bit of a reach but I am having an issue with the {subject}.aparc.32k_fs_LR.dlabel.nii files from HCP, I've looked all over the internet and found nothing. To extract the ROI mapping, this is essentially what I've done:
It works well, but it does not provide the same resaults I obtained from my matlab base file, which does something different by accessing a particular mapping like this:
The problem is that cifti in matlab obviously doesn't have the same implementation as nibabel library so I don't know how to access that specific "attribute" of the atlas with this library. Maybe someone has faced something similar before or has any guidance for me, thank you!!
The text was updated successfully, but these errors were encountered:
It's unclear to me what you're trying to do. What do you get out of your MATLAB code? Do you have an example file where you can show the differences in Python and MATLAB?
Hello! I think this may be a bit of a reach but I am having an issue with the {subject}.aparc.32k_fs_LR.dlabel.nii files from HCP, I've looked all over the internet and found nothing. To extract the ROI mapping, this is essentially what I've done:
def load_atlas_aux(path2atlas):
It works well, but it does not provide the same resaults I obtained from my matlab base file, which does something different by accessing a particular mapping like this:
subjlab = ft_read_cifti(path2atlas);
load_atlas_cmd = strcat('subjlab.x',subject,'_aparc');
segmentation_atlas = eval(load_atlas_cmd);
The problem is that cifti in matlab obviously doesn't have the same implementation as nibabel library so I don't know how to access that specific "attribute" of the atlas with this library. Maybe someone has faced something similar before or has any guidance for me, thank you!!
The text was updated successfully, but these errors were encountered: