Difference between revisions of "Bruker MRI"
Jump to navigation
Jump to search
(Created page with '==File Formats== Description of [http://imaging.mrc-cbu.cam.ac.uk/imaging/FormatBruker Bruker MRI data file formats]. Additional description taken from http://www.mriresearch.u…') |
(Fixed naming convention link) |
||
| Line 3: | Line 3: | ||
Description of [http://imaging.mrc-cbu.cam.ac.uk/imaging/FormatBruker Bruker MRI data file formats]. | Description of [http://imaging.mrc-cbu.cam.ac.uk/imaging/FormatBruker Bruker MRI data file formats]. | ||
| − | Additional description taken from http:// | + | Additional description taken from http://mriresearch.med.ubc.ca/facilities/7t-mri/researchers-guide/naming-conventions/ |
Each Experiment directory contains another subdirectory called pdata as well as several data files: | Each Experiment directory contains another subdirectory called pdata as well as several data files: | ||
Revision as of 15:21, 5 July 2017
File Formats
Description of Bruker MRI data file formats.
Additional description taken from http://mriresearch.med.ubc.ca/facilities/7t-mri/researchers-guide/naming-conventions/
Each Experiment directory contains another subdirectory called pdata as well as several data files:
- fid: the raw unreconstructed data file (i.e. the “k-space” time-domain data)
- method: text file containing the high-level acquisition parameters (e.g. number of pixels, measurement method, field of view, echo time, repetition time, number of averages, etc.)
- acqp: text file containing the base-level acquisition parameters (the method parameters are derived from these acqp parameters, which are a bit like the “machine-code” variables of the pulse sequence that was used)
- pulseprogram: text file containing the MRI sequence
- pdata folder: only exists for image data. It contains subdirectories corresponding to the different Processed Datasets of the current Experiment – each directory is named after the<ProcNo>(e.g.1,2,etc.). For the majority of cases,the“1”directory contains the processed image data. Files in “1” include the following:
- 2dseq: the processed image data, expressed in a raw binary format without header. If there are multiple slices in the dataset, they are usually stored contiguously. The default binary word type is 16 bit signed integer, little endian.
- Reco: text file including all reconstruction parameters