History of AFNI updates  

|
April 11, 2003 05:55PM
Is it OK to do this for an anatomy dataset that already has a +tlrc .HEAD file but no .BRIK? For example, in AFNI I can load in an anatomical dataset that has a +tlrc .HEAD file only, then switch the view to Talairach, then write it out using Write Anat. This will create a +tlrc .BRIK file.

From the command line, I can use the following command to create a new .BRIK & .HEAD file as well: "adwarp -apar anatomy+tlrc -dpar anatomy+orig -force".

The IDCODE_STRING in the +tlrc .HEAD files resulting from each method are different. Using the first method, the ID CODE_STRING in the +tlrc .HEAD file remains the same as before the +tlrc .BRIK file was created. Using the command line method, a new IDCODE_STRING is assigned to the +tlrc .HEAD file. The IDCODE_ANAT_PARENT and IDCODE_WARP_PARENT using either method are identical to the original +tlrc .HEAD file.

Will there be any problems because the IDCODE_STRING changes in the +tlrc .HEAD file in the second method using adwarp? Is there a better way to mimic the Write Func or Anat from the AFNI GUI?

Thanks!

Subject Author Posted

Save +orig in a different view from command line

Eric April 10, 2003 08:07PM

Re: Save +orig in a different view from command line

Christine Smith April 11, 2003 12:59AM

Re: Save +orig in a different view from command line

Eric April 11, 2003 05:55PM