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

Collect common functions/interfaces in separate package? #65

Open
tsalo opened this issue Sep 5, 2024 · 0 comments
Open

Collect common functions/interfaces in separate package? #65

tsalo opened this issue Sep 5, 2024 · 0 comments

Comments

@tsalo
Copy link
Collaborator

tsalo commented Sep 5, 2024

There are some steps that are probably going to be fairly common across fMRIPost workflows. I am trying to decide if those functions and interfaces should go in a separate package (e.g., nipostflows) or if I should just try to get them in niworkflows.

Starting a list:

  • Motion filtering to respiration-related noise
  • Interface to measure functional connectivity inflation over the course of the run
  • Interface to calculate QC-FC measures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant