You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use the mono_t2 model to fit t2 maps and use the OffsetTerm in the model, the results do not contain any information about the OffsetTerm.
This leads to inconsistencies. For example, using plotModel with data where there may be a significant offset present, there is a systematic discrepancy between data and fit. Neither FitResults nor equation() do consider the offset.
Expected Behavior
If OffsetTerm is used in mono_t2, it should propagate to the fit results and be considered in the plot.
Actual Behavior
the value of the offset term is not present in the fit results struct
the equation() function does not consider the offset term either and returns the equation without offset, which is equivalent to offset = 0
plotModel() also does not consider the offset, such that the behavior is as if offset = 0
Steps to Reproduce the Problem
acquire T2 data at low SNR
use mono_t2 with OffsetTerm enabled
look at FitResults: no offset value present. use plotModel(). the offset is not considered in the plot.
Specifications
Version: 2.4.2
Platform: windows with matlab 2023b
Subsystem: ?
The text was updated successfully, but these errors were encountered:
gabuzi
added a commit
to gabuzi/qMRLab
that referenced
this issue
Sep 27, 2023
If I use the mono_t2 model to fit t2 maps and use the OffsetTerm in the model, the results do not contain any information about the OffsetTerm.
This leads to inconsistencies. For example, using plotModel with data where there may be a significant offset present, there is a systematic discrepancy between data and fit. Neither FitResults nor equation() do consider the offset.
Expected Behavior
If OffsetTerm is used in mono_t2, it should propagate to the fit results and be considered in the plot.
Actual Behavior
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: