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
We're often processing data in batches - for whatever reason. However, if we iteratively use find_template_subject with different inputs, we have the risk of using different templates for sign-flipping different data.
Would it be an idea to add the following to find_template_subject - especially for when we interact with source_recon through the run_source_batch?
check if the source directory contains sign_flip_template.txt
If so, and if this subject folder is available load use this template subject (and add it to subjects for input to run_source_batch)
if not, run find_template_subject as usual
Of course we could add in an extra argument overwrite to not use the txt file
The text was updated successfully, but these errors were encountered:
Note, for anyone currently experiencing issues trying to align a dataset to a different already sign flipped dataset, there is an example using the low-level functions that can be used more flexibly:
The user can specify the template (which can be from another dataset) in osl-dynamics, rather than OSL. Note, it doesn't matter if the sign flipping was already done to another template beforehand.
We're often processing data in batches - for whatever reason. However, if we iteratively use
find_template_subject
with different inputs, we have the risk of using different templates for sign-flipping different data.Would it be an idea to add the following to
find_template_subject
- especially for when we interact with source_recon through therun_source_batch
?sign_flip_template.txt
subjects
for input torun_source_batch
)find_template_subject
as usualoverwrite
to not use the txt fileThe text was updated successfully, but these errors were encountered: