khanlab / khanlab/scattr

pybids_inputs_dwi doesn't provide snakebids CLI args for filtering

Open
#103 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
7
Forks
6
PR merge metrics
No merged PRs in 30d

Description

This makes running the pipeline difficult without updating the config. I see the motivation for this, eg to deal with the case where dwi and T1w data are from two different bids datasets, but I actually think that doesn't happen too often in practice -- e.g. it won't happen for raw bids datasets (I know scattr doesn't deal with raw yet), and for preprocessed datasets e.g. snakedwi or others, there would be both T1w and dwi in the derivatives dataset.

So I am thinking the better solution is to place everything in pybids_inputs. Also could set some sensible defaults (the current defaults are pretty specific and almost always would need to be overriden).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing pybids_inputs and the snakebids CLI argument handling, then compare them with the current config defaults described in the issue. Determine how filtering arguments and sensible defaults should be exposed without requiring config changes; done means the requested filtering can be controlled through the CLI and the defaults match the agreed behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.