Define global popups flag (as user input in GUI) to pass to all functions down the processing #116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
the pop up flag
job.subj.log.flags
is set on the GUI and isindependent
of what functions are called down the processing. Currently, each time one needs to record an error to hmri_log along with a popup (as set on the GUI), the specificjob.subj.log.flags
needs to be passed to the function in some way every single time. We solve this problem by extracting this user input withinhmri_run_create
into a global variable and then using this global variable directly to record the error messages within thehmri_calc_R2s
. We will be searching within the toolbox and using this method to implement all the error handling in the following format:observe that for instance these particular lines did not comply with the above, before the implementation here:
hMRI-toolbox/hmri_calc_R2s.m
Line 167 in 6123826
hMRI-toolbox/hmri_calc_R2s.m
Line 198 in 6123826
Tests performed
The following shows the content of the hmri_log file during manual testing for the implemented errors: