Skip to content

RFC: Change parameterize_dirs to default to False? #3496

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

Open
effigies opened this issue Jul 23, 2022 · 1 comment
Open

RFC: Change parameterize_dirs to default to False? #3496

effigies opened this issue Jul 23, 2022 · 1 comment

Comments

@effigies
Copy link
Member

Would you ever consider setting parameterize_dirs to false as a default in nipype? We are working on integrating MRIQC into CBRAIN (http://www.cbrain.ca/), and have run into an issue with file name lengths. While the solution posted above should hopefully work for this version of MRIQC, having this changed in nipype's defaults would make it so we don't have to implement this change in future containerized versions of MRIQC + limit the likelihood of this happening for other pipelines we work with. I would understand if there are negative repercussions of this change that would outweigh the potential utility. Thanks!

Originally posted by @erikglee in #2061 (comment)

I think the main repercussion is that working directories could stop being reusable with an upgrade in nipype. If there's general sentiment in this direction, I think we could do it in a minor release.

@effigies effigies changed the title Change parameterize_dirs to default to False RFC: Change parameterize_dirs to default to False? Jul 23, 2022
@effigies
Copy link
Member Author

Any opinions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant