Currently the processing/BIDS pipeline runners loop over available participant-session pairs, and the only way to run group-level processing/pipelines is to specify some arbitrary participant and session (which is a hack).
We can add a flag in the custom Boutiques configuration in descriptor files so that the pipeline developer can disable that looping (i.e., if that flag is on, then get_participants_sessions_to_run just returns [(None, None)]).
Currently the processing/BIDS pipeline runners loop over available participant-session pairs, and the only way to run group-level processing/pipelines is to specify some arbitrary participant and session (which is a hack).
We can add a flag in the custom Boutiques configuration in descriptor files so that the pipeline developer can disable that looping (i.e., if that flag is on, then
get_participants_sessions_to_runjust returns[(None, None)]).