devel > Sparse Data Storage (INTENT_NODE_INDEX) usage
Showing 1-2 of 2 posts
Nov 13, 2008 03:11 PM | Benjamin Thyreau
Sparse Data Storage (INTENT_NODE_INDEX) usage
Hi,
IIRC, chapter 6.0 of the April08 specification defines NIFTI_INTENT_NODE_INDEX as a DA intent-code to defines a specific set nodes, with the following DAs mapping these.
- Is there a way to specifies which mesh this node-set refers to ?
- Can i have several such set defined in a single Gifti file ? I'm proposing having such a DA pattern in the file : [ master_coord, node_index_1, [ da_matching_indices1 ]+, node_index_2, [ da_matching_indices2 ]+, ...
Thanks !
IIRC, chapter 6.0 of the April08 specification defines NIFTI_INTENT_NODE_INDEX as a DA intent-code to defines a specific set nodes, with the following DAs mapping these.
- Is there a way to specifies which mesh this node-set refers to ?
- Can i have several such set defined in a single Gifti file ? I'm proposing having such a DA pattern in the file : [ master_coord, node_index_1, [ da_matching_indices1 ]+, node_index_2, [ da_matching_indices2 ]+, ...
Thanks !
Mar 10, 2009 02:03 PM | Richard Reynolds
RE: Sparse Data Storage (INTENT_NODE_INDEX) usage
Hi Benjamin,
Sorry for being so slow...
Each file should have the same topology, at least. So while
these all may be based on the same parent surface, it would
not be recommended to put multiple NODE_INDEX lists in one
dataset.
- rick
Sorry for being so slow...
Each file should have the same topology, at least. So while
these all may be based on the same parent surface, it would
not be recommended to put multiple NODE_INDEX lists in one
dataset.
- rick