francescastrappini Wrote:
-------------------------------------------------------
> Hi Ziad, thank you!
>
> You were right, the dataset was wrong. I made a
> new one and displayed into SUMA. I looked at the
> timeseries as you suggested and it seems OK. I
> have a couple of questions:
>
> 1. I can display correctly the dataset after
> 3dVol2Surf, but after performing ConvertDset with
> the option -pad_to_node ld120 I can't visualize it
> anymore. SUMA gives me this error: "Error
> SUMA_OKassign: Node index range outise 0 and
> SO->N_Node, Error SUMA_LoadDsetOntoSO_eng: Cannot
> assign dsetto SO or its local domain parent."
Hi Francesca,
Sorry for the delay, you happen to post while I am traveling! This error message cannot be ignored. What -pad_to_node ld120 does, is create a dataset that has an entry for each of the nodes making up an icosahedron created with the -ld 120 option. Such an icosahedron defines a standard mesh for surfaces having 144'002 vertices. The surfaces onto which you are loading the dataset have less than 144'002 vertices for sure. I suspect you are using the original mesh surfaces or surfaces created with a lower mesh density. -- which spec file did you use when launching SUMA ?
You could replace ld120 with 0 and that should work fine (see help output for option -pad_to_node)
> Nevertheless, I was able to use 3dmaskdump and
> extract the voxel-wise timeseries from the the
> dataset after ConvertDset.
>
You'll need to repeat that step.
> 2. I can display the region when is in 1D.roi
> format but after I mapped it to the surface in the
> format 1D.dset I can't display it anymore
And that step
>
> Best
> Francesca
cheers
z