The main function adds additional paths as strings (?). I keep using cell strings specified in a call script to specify additional paths. This is a change that keeps getting reverted [e.g., 3989fe014bdc9e8fd41bd216ea6dcd1ffcbcd9a1], presumably because it is incompatible with the current yaml specification. To integrate, the function that reads the config.yaml should also turn additional paths in cellstrings.
https://github.com/Donders-Institute/PRESTUS/blob/05146df2186feee700709b48727170f2c47fbc5b/single_subject_pipeline.m#L50
The main function adds additional paths as strings (?). I keep using cell strings specified in a call script to specify additional paths. This is a change that keeps getting reverted [e.g., 3989fe014bdc9e8fd41bd216ea6dcd1ffcbcd9a1], presumably because it is incompatible with the current yaml specification. To integrate, the function that reads the config.yaml should also turn additional paths in cellstrings.
I'll look into it.