inversion_recovery: Compute a T1 map using Inversion Recovery data¶

https://mybinder.org/badge_logo.svg

Contents

% This m-file has been automatically generated using qMRgenBatch(inversion_recovery)
% for publishing documentation.
% Command Line Interface (CLI) is well-suited for automatization
% purposes and Octave.
%
% Please execute this m-file section by section to get familiar with batch
% processing for inversion_recovery on CLI.
%
% Demo files are downloaded into inversion_recovery_data folder.
%
% Written by: Agah Karakuzu, 2017
% ==============================================================================

1. Print inversion_recovery information

qMRinfo('inversion_recovery');
 inversion_recovery: Compute a T1 map using Inversion Recovery data

Assumptions:
(1) Gold standard for T1 mapping
(2) Infinite TR

Inputs:
IRData      Inversion Recovery data (4D)
(Mask)      Binary mask to accelerate the fitting (OPTIONAL)

Outputs:
T1          transverse relaxation time [ms]
b           arbitrary fit parameter (S=a + b*exp(-TI/T1))
a           arbitrary fit parameter (S=a + b*exp(-TI/T1))
idx         index of last polarity restored datapoint (only used for magnitude data)
res         Fitting residual


Protocol:
IRData  [TI1 TI2...TIn] inversion times [ms]
TimingTable   [TR] repetition time [ms]

Options:
method          Method to use in order to fit the data, based on whether complex or only magnitude data acquired.
'complex'     Complex dataset.
'magnitude'   Magnitude dataset.


fitModel        T1 fitting moddel.
'Barral'      Fitting equation: a+bexp(-TI/T1)
'General'     Fitting equation: c(1-2exp(-TI/T1)+exp(-TR/T1))

Example of command line usage (see also showdemo inversion_recovery_batch):
Model = inversion_recovery;  % Create class from model
Model.Prot.IRData.Mat=[350.0000; 500.0000; 650.0000; 800.0000; 950.0000; 1100.0000; 1250.0000; 1400.0000; 1700.0000];
data = struct;  % Create data structure
data.MET2data ='IRData.mat';  % Load data
data.Mask = 'Mask.mat';
FitResults = FitData(data,Model); %fit data
FitResultsSave_mat(FitResults);

For more examples: qMRusage(inversion_recovery)

Author: Ilana Leppert, 2017

References:
Please cite the following if you use this module:
A robust methodology for in vivo T1 mapping. Barral JK, Gudmundson E, Stikov N, Etezadi-Amoli M, Stoica P, Nishimura DG. Magn Reson Med. 2010 Oct;64(4):1057-67. doi: 10.1002/mrm.22497.
In addition to citing the package:
Karakuzu A., Boudreau M., Duval T.,Boshkovski T., Leppert I.R., Cabana J.F.,
Gagnon I., Beliveau P., Pike G.B., Cohen-Adad J., Stikov N. (2020), qMRLab:
Quantitative MRI analysis, under one umbrella doi: 10.21105/joss.02343

Reference page in Doc Center
doc inversion_recovery


2. Setting model parameters

2.a. Create inversion_recovery object

Model = inversion_recovery;

2.b. Set protocol and options

Protocol: MRI acquisition parameters that are accounted for by the respective model.

For example: TE, TR, FA FieldStrength. The assigned protocol values are subjected to a sanity check to ensure that they are in agreement with the data attributes.

Options: Fitting preferences that are left at user's discretion.

For example: linear fit, exponential fit, drop first echo.

2.b.1 Set protocol the CLI way

If you are using Octave, or would like to serialize your operations any without GUI involvement, you can assign protocol directly in CLI:

TI = [350.0000; 500.0000; 650.0000; 800.0000; 950.0000; 1100.0000; 1250.0000; 1400.0000; 1700.0000];
% TI(ms) is a vector of [9X1]
Model.Prot.IRData.Mat = [ TI];
TR = 2500;
Model.Prot.TimingTable.Mat = [ TR];

  See the generic notes section below for further information.

2.b.2 Set protocol and options the GUI way

The following command opens a panel to set protocol and options (if GUI is available to the user):

Model = Custom_OptionsGUI(Model);

If available, you need to close this panel for the remaining of the script to proceed.

  Using this panel, you can save qMRLab protocol files that can be used in both interfaces. See the generic notes section below for details.

3. Fit MRI data

3.a. Load input data

This section shows how you can load data into a(n) inversion_recovery object.

  • At the CLI level, qMRLab accepts structs containing (double) data in the fields named in accordance with a qMRLab model.

  See the generic notes section below for BIDS compatible wrappers and scalable
      qMRLab workflows.

%          |- inversion_recovery object needs 2 data input(s) to be assigned:
%          |-   IRData
%          |-   Mask

data = struct();

% IRData.mat contains [128  128    1    9] data.
load('inversion_recovery_data/IRData.mat');
% Mask.mat contains [128  128] data.
load('inversion_recovery_data/Mask.mat');
data.IRData= double(IRData);
data.Mask= double(Mask);

3.b. Execute fitting process

This section will fit the loaded data.

FitResults = FitData(data,Model,0);

Visit the generic notes section below for instructions to accelerate fitting by
      parallelization using ParFitData.

3.c. Display FitResults

You can display the current outputs by:

qMRshowOutput(FitResults,data,Model);

A representative fit curve will be plotted if available.

To render images in this page, we will load the fit results that had been saved before. You can skip the following code block;

% Load FitResults that comes with the example dataset.
FitResults_old = load('FitResults/FitResults.mat');
qMRshowOutput(FitResults_old,data,Model);

3.d. Save fit results

Outputs can be saved as *.nii.(gz) if NIfTI inputs are available:

% Generic function call to save nifti outputs
FitResultsSave_nii(FitResults, 'reference/nifti/file.nii.(gz)');

If not, FitResults.mat file can be saved. This file contains all the outputs as workspace variables:

% Generic function call to save FitResults.mat
FitResultsSave_mat(FitResults);

  FitResults.mat files can be loaded to qMRLab GUI for visualization and ROI
       analyses
.

The section below will be dynamically generated in accordance with the example data format (mat or nii). You can substitute FitResults_old with FitResults if you executed the fitting using example dataset for this model in section 3.b..

FitResultsSave_mat(FitResults_old);

3.e. Re-use or share fit configuration files

qMRLab's fit configuration files (inversion_recovery_Demo.qmrlab.mat) store all the options and protocol in relation to the used model and the release version.

  *.qmrlab.mat files can be easily shared with collaborators to allow them fit their own
      data or run simulations using identical option and protocol configurations.

Model.saveObj('my_inversion_recovery_config.qmrlab.mat');

4. Simulations

4.a. Single Voxel Curve

Simulates single voxel curves
  1. Analytically generate synthetic MRI data
  2. Add rician noise
  3. Fit and plot the respective curve

      x = struct;
x.T1 = 600;
x.rb = -1000;
x.ra = 500;
% Set simulation options
Opt.SNR = 50;
Opt.T1 = 600;
Opt.M0 = 1000;
Opt.TR = 3000;
Opt.FAinv = 180;
Opt.FAexcite = 90;
Opt.Updateinputvariables = false;
% run simulation
figure('Name','Single Voxel Curve Simulation');
FitResult = Model.Sim_Single_Voxel_Curve(x,Opt);

4.b. Sensitivity Analysis

Simulates sensitivity to fitted parameters
  1. Iterate fitting parameters from lower (lb) to upper (ub) bound
  2. Run Sim_Single_Voxel_Curve for Nofruns times
  3. Compute the mean and std across runs

            T1            rb            ra
      OptTable.st = [6e+02         -1e+03        5e+02]; % nominal values
OptTable.fx = [0             1             1]; %vary T1...
OptTable.lb = [0.0001        -1e+04        0.0001]; %...from 0.0001
OptTable.ub = [5e+03         0             1e+04]; %...to 5000
Opt.SNR = 50;
Opt.Nofrun = 5;
% run simulation
SimResults = Model.Sim_Sensitivity_Analysis(OptTable,Opt);
figure('Name','Sensitivity Analysis');
SimVaryPlot(SimResults, 'T1' ,'T1' );

5. Notes

5.a. Notes specific to inversion_recovery

5.a.1 BIDS

|== sub-01/
|~~~~~~ anat/
|---------- sub-01_inv-1_IRT1.json
|---------- sub-01_inv-1_IRT1.nii.gz
|---------- sub-01_inv-2_IRT1.json
|---------- sub-01_inv-2_IRT1.nii.gz
|---------- .
|---------- .
|---------- sub-01_inv-N_IRT1.json
|---------- sub-01_inv-N_IRT1.nii.gz
|
|== derivatives/
|~~~~~~ qMRLab/
|---------- dataset_description.json
|~~~~~~~~~~ sub-01/anat/
|-------------- sub-01_T1map.nii.gz
|-------------- sub-01_T1map.json
|-------------- sub-01_R1map.nii.gz
|-------------- sub-01_R1map.json
|-------------- sub-01_M0map.nii.gz
|-------------- sub-01_M0map.json

For further information, please visit BIDS qMRI Appendix.

5.b. Generic notes

5.b.1. Batch friendly option and protocol conventions

If you would like to load a desired set of options / protocols programatically, you can use *.qmrlab.mat files. To save a configuration from the protocol panel of inversion_recovery, first open the respective panel by running the following command in your MATLAB command window (MATLAB only):

Custom_OptionsGUI(inversion_recovery);

In this panel, you can arrange available options and protocols according to your needs, then click the save button to save my_inversion_recovery.qmrlab.mat file. This file can be later loaded into a inversion_recovery object in batch by:

Model = inversion_recovery;
Model = Model.loadObj('my_inversion_recovery.qmrlab.mat');

  Model.loadObj('my_inversion_recovery.qmrlab.mat') call won't update the fields in the Model object, unless the output is assigned to the object as shown above. This compromise on convenience is to retain Octave CLI compatibility.

If you don't have MATLAB, hence cannot access the GUI, two alternatives are available to populate options:

  1. Use qmrlab/mcrgui:latest Docker image to access GUI. The instructions are available here.
  2. Set options and protocols in CLI:
  • List available option fields using tab completion in Octave's command prompt (or window)
Model = inversion_recovery;
Model.option. % click the tab button on your keyboard and list the available fields.
  • Assign the desired field. For example, for a mono_t2 object:
Model = mono_t2;
Model.options.DropFirstEcho = true;
Model.options.OffsetTerm = false;

Some option fields may be mutually exclusive or interdependent. Such cases are handled by the GUI options panel; however, not exposed to the CLI. Therefore, manual CLI options assignments may be challenging for some involved methods such as qmt_spgr or qsm_sb. If above options are not working for you and you cannot infer how to set options solely in batch, please feel free to open an issue in qMRLab and request the protocol file you need.

Similarly, in CLI, you can inspect and assign the protocols:

Model = inversion_recovery;
Model.Prot. % click the tab button on your keyboard and list the available fields.

Each protocol field has two subfields of Format and Mat. The first one is a cell indicating the name of the protocol parameter (such as EchoTime (ms)) and the latter one contains the respective values (such as 30 x 1 double array containing EchoTimes).

The default Mat protocol values are set according to the example datasets served via OSF.

5.b.2 Parallelization

Beginning from release 2.5.0, you can accelerate fitting for the voxelwise models using parallelization.

Available in MATLAB only. Requires parallel processing toolbox.

In CLI, you can perform parallel fitting by:

parpool();
FitResults = ParFitData(data,Model);

If a parpool exists, the ParFitData will use it. If not, a new pool will be created using the local profile. By default, ParFitData saves outputs automatically every 5 minutes. You can disable this feature by:

FitResults = ParFitData(data, Model, 'AutosaveEnabled', false);

Alternatively, you can change the autosave interval (min 1 min) by:

FitResults = ParFitData(data,Model,'AutoSaveInterval',10);

If something went wrong during the fitting (e.g. your computer had to be restarted), you can recover the autosaved data by:

FitResults = ParFitData(data,Model,'RecoverDirectory','/ParFitTempResults_*/folder/from/the/previous/session');

GUI users will be prompted a question about whether they would like to use parallelization after clicking the Fit Data button, if the conditions are met. When called from GUI, ParFitData will be run with default options:

  • Save temporary results every 5 minutes or whenever a chunk has finished processing
  • Split data into chunks with a granularity factor of 3
  • Do not remove temporary fit results upon completion

For further information:

help ParFitData

The default parallelization options can be changed in the preferences.json file located at the root qMRLab directory.

6. Citations

qMRLab JOSS article

Karakuzu A., Boudreau M., Duval T.,Boshkovski T., Leppert I.R., Cabana J.F., Gagnon I., Beliveau P., Pike G.B., Cohen-Adad J., Stikov N. (2020), qMRLab: Quantitative MRI analysis, under one umbrella 10.21105/joss.02343

Reference article for inversion_recovery

Barral, J.K., et al. (2010). A robust methodology for in vivo T1 mapping. Magnetic Resonance in Medicine, 64(4), 1057-1067. 10.1002/mrm.22497


Quantitative MRI, under one umbrella.

| qMRPullseq | qMRFlow | Interactive Tutorials |

NeuroPoly Lab, Montreal, Canada