-
Notifications
You must be signed in to change notification settings - Fork 19
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
Requested metric: respiratory-volume-per-time #1
Comments
@tsalo thank you for the request. The implementation of this approach, along with its counterpart for variations in cardiac rate also described in this paper, is within our plans for phys2denoise |
I have functions sitting around for RV and RVT. I would be happy to open PRs for them to phys2denoise if you can give me an idea of how the package will be structured, so I know where to put them. |
HI @tsalo , |
The main thing I'm pondering is whether each metric should be on its own (i.e. the user should be able to invoke each of them via a command) or they should be argument of a general workflow (i.e. the user should call |
I personally would end up calling them within Python, but for the CLI it might be good to have an argument that can take multiple values (e.g., |
Agree with this suggestion |
@smoia I posted about the infrastructure in the Gitter channel, but can open a separate issue here if you'd prefer. |
Move metric call function to metrics.utils
Respiratory-volume-per-time (RVT) is a "breath-to-breath metric of respiratory variation," and can be used to generate a regressor for denoising fMRI data.
Per Chang and Glover (2009):
A relevant metric is RPV convolved with a respiratory response function:
RVT*RRF is also often lagged when used to denoise fMRI data.
The text was updated successfully, but these errors were encountered: