-
Notifications
You must be signed in to change notification settings - Fork 13
Description
Description
Probably related to #1103 . In short, due to the "_#" approach, the SESSION symbol can't be resolved when it is requested to do so within xASL_init_iteration -> runIteration. Error happens around this block:
% Optional diary logfile of command window
if ~isempty(diaryFile)
% NB. Don't overwrite diaryFile itself because it might be expanded
% with different values in the next iteration.
diaryFileEx = xASL_adm_ReplaceSymbols(diaryFile,x);
diaryFileEx = fullfile(diaryFileEx);HENK: This is not related to #1103. And the problem was probably the diaryFile name, which defaults to having sessions as well, which LongReg doesn't have. This should now be fixed. Can you try if it works for you now? Next time I hope I will fix this faster than 6 months, polease nudge me next time!
Tasks
- Fix SESSION field in
xstruct by the timexASL_adm_ReplaceSymbolsis called before running longitudinal registration
HENK: THIS WAS NOT THE ISSUE, IT WAS THE WRONG DIARY FILE that incorrectly includedx.SESSIONS - See if this can be addressed as well Error by Unrecognized field name "STRUCT" #1232 (reply in thread)
-
xASL_init_Iteration: fixdiaryFilefor LongReg - HENK: I did some revamping in the mean time: capital-insensitive (
strcmpi,regexpi)
OS path delimiter independency:fullfileinstead of/
How to test
-
Checkout
developbranch. -
Run a dataset with multiple visits. Example given below, which successfully completed the Structural Module and is about to execute the LongReg module:
-
In dataPar.json,
x.modules.bRunLongRegis set to 1. Run with only the Structural module selected. -
Breakpoint at line 304 in
xASL_init_Iterationwhenjobfnis @xASL_module_LongReg. (workspace attached)
LongRegBugSESSIONSymbol__xASL_init_Iteration.zip
Release notes
Fix <SESSION> symbol interpretation in longitudinal registration.
