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  

|
February 15, 2014 01:03PM
Hi Kara,

kblacker Wrote:
-------------------------------------------------------
> I tried to use
> ConvertDsets as you suggested but I am getting an
> error that I can't figure out. Below is my script
> and the error message:
>
> Script:
> foreach subj ( p01 p02 p03 p04 p05 p06 p07 p08 p10
> p11 p14 p15 p16 )
> cd /Volumes/KaraData/fSIR/$subj/$subj.results
> foreach hemi ( lh rh )
> ConvertDset -input
> /Volumes/KaraData/fSIR/$subj/$subj.results/WMstats
> .$subj.$hemi.niml.dset \
> -pad_to_node MAX_INDEX \
> -prefix WMstats.$subj.$hemi.PADDED
> end
> end
> […]
> ConvertDset -input
> /Volumes/KaraData/fSIR/p01/p01.results/WMstats.p01
> .rh.niml.dset -pad_to_node MAX_INDEX -prefix
> WMstats.p01.rh.PADDED
> ++ Notice ConvertDset (SUMA_ConvertDset.c:743
> @10:59:34):
> Padding output dset until node 130445
> Error SUMA_Set_Sub_String (suma_utils.c:3592):
> NULL input
> Warning SUMA_AddDsetNodeIndexColAttr:
> Failed to set substring for COLMS_LABS at 0
> end

That's a somewhat weird error. It suggests it was unable to set the labels for each 'sub-brik' (sample) in your data, but it's unclear why that would be the case.
What does "SurfDsetInfo /Volumes/KaraData/fSIR/p01/p01.results/WMstats.p01.rh.niml.dset" give you?

Another note: you used "-pad_to_node MAX_INDEX", which does not seem appropriate. With MAX_INDEX it pads up to the last node in the dataset that has data, but it can be the case that there are nodes beyond that (without data).
Indeed, when using MapIcosahedron surfaces with "ld" linear divisions, the number of nodes is (ld*ld)*10+2, and the parameter for -pad_to_node has to be one less than that (=(ld*ld)*10+1) because SUMA uses 0-based indexing. Thus the pad_to_node value has to have a '1' in the rightmost position, unlike the number 130445 which ConvertDset uses.
To find the number of nodes in your surfaces, either compute the number of nodes using the ld value that you used, or open a surface anatomical (.asc) file and find the first line not starting with '#'. It should have two numbers; the first one is the number of nodes. Again, you would have to subtract one from the number of nodes to get the required value for -pad_to_node.

Hope that helps,
Nick
Subject Author Posted

when and how to use standard meshes in SUMA

kblacker February 13, 2014 10:13AM

Re: when and how to use standard meshes in SUMA

nick February 13, 2014 10:54AM

Re: ConvertDsets error

kblacker February 15, 2014 11:23AM

Re: ConvertDsets error

nick February 15, 2014 01:03PM

Re: ConvertDsets error

kblacker February 17, 2014 09:37AM

Re: ConvertDsets error

nick February 17, 2014 10:49AM

Re: when and how to use standard meshes in SUMA

ziad February 15, 2014 05:58PM

Re: when and how to use standard meshes in SUMA

kblacker February 17, 2014 09:41AM

Re: when and how to use standard meshes in SUMA

kblacker February 18, 2014 01:30PM

Re: when and how to use standard meshes in SUMA

ziad February 19, 2014 08:38PM

Re: when and how to use standard meshes in SUMA

kblacker February 20, 2014 10:50AM

Re: when and how to use standard meshes in SUMA

rick reynolds February 20, 2014 11:05AM

Re: when and how to use standard meshes in SUMA

ziad February 20, 2014 11:28AM