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.

Sign up for GitHub

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

Jump to bottom

set_confound vs set_confounds #312

Open
gerasy1987 opened this issue Dec 12, 2023 · 0 comments
Open

set_confound vs set_confounds #312

gerasy1987 opened this issue Dec 12, 2023 · 0 comments

Comments

@gerasy1987
Copy link
Collaborator

It seems that set_confounds is a leftover function that is superseded by set_confound but is not exported anymore. Is there a reason to keep it? I checked throughout the package and it seems that it can be removed completely. If it is intentionally left to allow users both spellings, then I think it should be exported as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gerasy1987