Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fmriprep-ingress regressor naming issue #2076

Open
sgiavasis opened this issue Feb 21, 2024 · 0 comments
Open

fmriprep-ingress regressor naming issue #2076

sgiavasis opened this issue Feb 21, 2024 · 0 comments
Assignees
Milestone

Comments

@sgiavasis
Copy link
Collaborator

sgiavasis commented Feb 21, 2024

With @e-kenneally 's idea, I'm picturing something like this:

  1. Have a field you can place in the regressor selector (under each strategy) that is like "include_from_confounds:" or something and it's a list of column names that can be found in the ingressed confounds TSV that comes in from the output directory; if left blank or isn't present, the default is to include all (even if this crashes 3dTproject)
  2. This functionality will filter the ingressed confounds TSV first - with a function node, maybe using Pandas ideally; drop the columns not included in the list
  3. If there are other regressors in the selector for that strategy, now have it such that they are added to this filtered/reduced TSV
  4. Send that merged TSV to the RPool as desc-confounds_timseries
@sgiavasis sgiavasis converted this from a draft issue Feb 21, 2024
@sgiavasis sgiavasis added this to the 1.8.7 release milestone Feb 21, 2024
@sgiavasis sgiavasis moved this from 🏗 In progress to 👀 In review in C-PAC Development Mar 18, 2024
@sgiavasis sgiavasis moved this from 👀 In review to Close on release in C-PAC Development Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Close on release
Development

No branches or pull requests

2 participants