|
Tutorial: data import to CaminoTutorials.RawDataTutorial HistoryHide minor edits - Show changes to markup July 06, 2010, at 09:26 PM
by
- Changed lines 20-21 from:
Converting DICOM datato:
Converting DICOM dataChanged line 25 from:
Limitations on image format support in Caminoto:
Limitations on image format support in CaminoJuly 06, 2010, at 08:22 PM
by
- Changed lines 3-4 from:
Dealing with image datato:
DWI data - supported image formatsChanged line 22 from:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to to:
Camino doesn't have any support for reading DICOM data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to July 06, 2010, at 08:21 PM
by
- Changed lines 3-29 from:
to:
Dealing with image dataIf you have data in Analyze, MetaIO, or NIfTI format, you can convert it directly to voxel order using image2voxel -4dimage ScannerOrder.hdr | dtfit - schemefile
Here, Sometimes we may have or want 3D volumes instead of one 4D image. For example, we might want to coregister all the DWI volumes to correct for motion. You can split them with split4dnii -inputfile image.nii -outputroot 3d_
produces 3d_0001.nii through 3d_0060.nii. To use these images with image2voxel, do something like ls 3d_* > imagelist.txt; image2voxel -imagelist imagelist.txt
Converting DICOM dataCamino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to Limitations on image format support in CaminoCamino will read .nii, .hdr, or .mha files, but it will only read the raw data on its original voxel grid, which is assumed to be RAS, ie the data is packed on disk with x increasing left to right, y posterior to anterior, and z inferior to superior. We don't yet have the ability to apply header transformations or reordering of the data. Changed lines 32-34 from:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, or the data type. If you have image data (eg Analyze, NIfTI), many of these tasks can be done for you, see the section on to:
Raw data can be manipulated in various ways. You may need to change the ordering of data, the endianness, or the data type. Deleted lines 57-83:
Dealing with image dataIf you have data in Analyze, MetaIO, or NIfTI format, you can convert it directly to voxel order using image2voxel -4dimage ScannerOrder.hdr | dtfit - schemefile
Here, Sometimes we may have or want 3D volumes instead of one 4D image. For example, we might want to coregister all the DWI volumes to correct for motion. You can split them with split4dnii -inputfile image.nii -outputroot 3d_
produces 3d_0001.nii through 3d_0060.nii. To use these images with image2voxel, do something like ls 3d_* > imagelist.txt; image2voxel -imagelist imagelist.txt
Converting DICOM dataCamino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to Limitations on image format support in CaminoCamino will read .nii, .hdr, or .mha files, but it will only read the raw data on its original voxel grid, which is assumed to be RAS, ie the data is packed on disk with x increasing left to right, y posterior to anterior, and z inferior to superior. We don't yet have the ability to apply header transformations or reordering of the data. July 06, 2010, at 05:35 PM
by
- Changed lines 20-22 from:
By default, DWI data is expected to be Processed raw image data is assumed to be to:
By default, DWI data is expected to be Processed raw image data is assumed to be July 06, 2010, at 05:33 PM
by
- Changed line 18 from:
Data typeto:
Data typeJuly 06, 2010, at 05:19 PM
by
- Added line 3:
Added line 8:
Changed lines 11-12 from:
Probably the most common task is to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task is to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the Added lines 17-24:
Data typeBy default, DWI data is expected to be Processed raw image data is assumed to be Added line 55:
April 27, 2010, at 11:27 PM
by
- Changed line 13 from:
Where to:
where April 27, 2010, at 11:25 PM
by
- Changed line 13 from:
Where to:
Where April 27, 2010, at 11:25 PM
by
- Changed line 13 from:
Where to:
Where April 27, 2010, at 11:24 PM
by
- Changed line 13 from:
Where to:
Where April 27, 2010, at 11:23 PM
by
- Changed line 13 from:
Where to:
Where April 27, 2010, at 11:23 PM
by
- Added lines 12-13:
Where April 27, 2010, at 11:18 PM
by
- Changed line 42 from:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to to:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to April 27, 2010, at 11:17 PM
by
- Changed line 23 from:
Dealing with image data.to:
Dealing with image dataApril 27, 2010, at 10:05 PM
by
- Changed line 9 from:
Probably the most common task is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task is to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the April 27, 2010, at 10:05 PM
by
- Changed line 9 from:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the April 27, 2010, at 10:04 PM
by
- Changed line 51 from:
If you have NIfTI tensor data, you can convert it with @@niftidt2camino: to:
If you have NIfTI tensor data, you can convert it with April 27, 2010, at 10:04 PM
by
- Changed lines 9-10 from:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the Changed line 25 from:
If you have data in Analyze, MetaIO, or NIfTI format, you can convert it directly to voxel order using to:
If you have data in Analyze, MetaIO, or NIfTI format, you can convert it directly to voxel order using April 27, 2010, at 10:04 PM
by
- Changed lines 52-55 from:
[@ niftidt2camino -inputfile dt.nii > dt.Bdouble
to:
niftidt2camino -inputfile dt.nii > dt.Bdouble
The NIfTI tensor format contains a bit less information than the Camino format (ie, no exit code or unweighted signal), so these will be blank in the output unless you provide them on the command line. You can convert back to NIfTI format with April 27, 2010, at 10:01 PM
by
- Changed lines 31-39 from:
to:
Sometimes we may have or want 3D volumes instead of one 4D image. For example, we might want to coregister all the DWI volumes to correct for motion. You can split them with split4dnii -inputfile image.nii -outputroot 3d_
produces 3d_0001.nii through 3d_0060.nii. To use these images with image2voxel, do something like ls 3d_* > imagelist.txt; image2voxel -imagelist imagelist.txt
Changed lines 42-43 from:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to to:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to Changed lines 49-52 from:
NIfTI tensor datato:
NIfTI tensor dataIf you have NIfTI tensor data, you can convert it with @@niftidt2camino: [@ niftidt2camino -inputfile dt.nii > dt.Bdouble
April 27, 2010, at 09:47 PM
by
- Changed line 34 from:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. to:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. This program will give you a 4D nii file that you can feed to April 27, 2010, at 09:45 PM
by
- Added line 22:
Deleted line 31:
Added lines 33-34:
Camino doesn't have any support for reading scanner data, so we use dcm2nii, which is part of the mricron package by Chris Rorden. April 27, 2010, at 09:37 PM
by
- Changed lines 5-6 from:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, the data type, or extract a subset of the data set. If you have image data (eg Analyze, NIfTI), many of these tasks can be done for you, see the section on to:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, or the data type. If you have image data (eg Analyze, NIfTI), many of these tasks can be done for you, see the section on Added lines 24-31:
If you have data in Analyze, MetaIO, or NIfTI format, you can convert it directly to voxel order using image2voxel -4dimage ScannerOrder.hdr | dtfit - schemefile
Here, Changed lines 34-36 from:
NIfTI support in CaminoNIfTI raw datato:
Limitations on image format support in CaminoCamino will read .nii, .hdr, or .mha files, but it will only read the raw data on its original voxel grid, which is assumed to be RAS, ie the data is packed on disk with x increasing left to right, y posterior to anterior, and z inferior to superior. We don't yet have the ability to apply header transformations or reordering of the data. April 27, 2010, at 09:29 PM
by
- Changed lines 15-16 from:
Following Java convention, Camino writes raw data in big-endian format. Camino will never write little-endian data except when writing images with headers that indicate endianness (eg, when writing an Analyze header). When reading data, Camino assumes big-endian input unless told otherwise by an image header. Therefore if the file to:
Following Java convention, Camino writes raw data in big-endian format. Camino will never write little-endian data except when writing images with headers that indicate endianness (eg, when writing an Analyze header). When reading data, Camino assumes big-endian input unless told otherwise by an image header. Therefore if the file Added line 20:
The April 27, 2010, at 09:23 PM
by
- Changed lines 9-19 from:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the scanner2voxel -voxels 983040 -components 60 -inputfile ScannerOrder.img -inputdatatype short > VoxelOrder.Bfloat
EndiannessFollowing Java convention, Camino writes raw data in big-endian format. Camino will never write little-endian data except when writing images with headers that indicate endianness (eg, when writing an Analyze header). When reading data, Camino assumes big-endian input unless told otherwise by an image header. Therefore if the file cat ScannerOrder.img | shredder 0 -2 0 | scanner2voxel -voxels 983040 -components 60 \\ -inputdatatype short > VoxelOrder.Bfloat April 27, 2010, at 09:13 PM
by
- Changed line 9 from:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the to:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the April 27, 2010, at 09:12 PM
by
- Changed lines 5-6 from:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, the data type, or extract a subset of the data set. to:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, the data type, or extract a subset of the data set. If you have image data (eg Analyze, NIfTI), many of these tasks can be done for you, see the section on Changed lines 9-11 from:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. Image2voxelto:
Probably the most common task you'll need to do is to to re-order data from image to voxel order. In scanner order or image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. You can get into and out of scanner order with the Dealing with image data.April 27, 2010, at 09:04 PM
by
- Changed lines 7-13 from:
DICOM datato:
Ordering dataProbably the most common task you'll need to do is to to re-order data from image to voxel order. In image order, multi-component images are stored as consecutive volumes. This is convenient for visualization, since you can easily render a particular 3D volume. It is inconvenient for parallel processing, as you must read the entire 4D image in order to get the components for a particular processing. Data in voxel order stores all components for a particular voxel together. Thus you can read the image one voxel at a time, or skip ahead to particular voxel, without reading the entire image into memory. Camino does most of its I/O in voxel order. Image2voxelConverting DICOM dataApril 27, 2010, at 08:32 PM
by - April 27, 2010, at 06:06 PM
by - April 27, 2010, at 06:06 PM
by - April 27, 2010, at 06:06 PM
by - April 27, 2010, at 06:06 PM
by
- Added lines 4-5:
Raw data can be manipulated in various ways. You may wish to change the ordering of data, the endianness, the data type, or extract a subset of the data set. April 27, 2010, at 05:42 PM
by
- Changed lines 3-11 from:
Coming soon to:
Dealing with raw dataDICOM dataNIfTI support in CaminoNIfTI raw dataNIfTI tensor dataApril 27, 2010, at 04:25 PM
by
- Added lines 1-3:
(:title Tutorial: data import to Camino:) Coming soon |