Enable different set of bolds for each session in TransmitLong#376
Enable different set of bolds for each session in TransmitLong#376
Conversation
|
Just an observation that my initial thought is that we'd want to use So, the heuristic that we've adopted instead is that |
|
|
||
| #PseudoTransmit-specific. Should be the same as in the corresponding cross-sectional calls. | ||
| opts_AddOptional '--pt-fmri-names' 'fMRINames' 'rfMRI_REST1_LR@rfMRI_REST1_RL...' "fmri runs to use SE/SBRef files from, separated by @" | ||
| opts_AddOptional '--pt-fmri-names' 'fMRINames' 'rfMRI_REST1_LR@rfMRI_REST1_RL...' "fmri runs to use SE/SBRef files from, separated by @. For per-session lists, separate session-specific sets using % (e.g., run1@run2%run2%run1@run3)." |
There was a problem hiding this comment.
| opts_AddOptional '--pt-fmri-names' 'fMRINames' 'rfMRI_REST1_LR@rfMRI_REST1_RL...' "fmri runs to use SE/SBRef files from, separated by @. For per-session lists, separate session-specific sets using % (e.g., run1@run2%run2%run1@run3)." | |
| opts_AddOptional '--pt-fmri-names' 'fMRINames' 'rfMRI_REST1_LR@rfMRI_REST1_RL...' "fmri runs to use SE/SBRef files from, separated by @. For per-session lists, separate session-specific sets using % (e.g., run1@run2%run2%run1@run3 to use run1 and run2 from session1, run2 from session2, and run1 and run3 from session3)." |
There was a problem hiding this comment.
Suggested a bit more wording to make the example very explicit.
Currently TransmitBiasLong assumes that all the sessions have the exact same set of fMRI images. This often is not the case in longitudinal datasets. This PR enables specifying different set of fMRI images for each session while keeping backward compatibility with old behavior. If a user desires to specify different set of fMRI images for each session, they list fMRI names for each session in the
--pt-fmri-namesargument, separating sessions with%character. If no%character is present, the same set of fMRI names is used for all sessions. If%character is present, the code checks whether the number of fMRI sets match the number of sessions, and uses the sets in the same order as the sessions are listed.In the example:
the pairings are:
session1–rest,taskA, andtaskB,session2–rest,taskAsession3–rest,taskB