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

[ENH] Separate converters and iotools in separate modules #1443

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

NicolasGensollen
Copy link
Member

Description

This PR investigates the architectural change of having converters and iotools in their own modules instead of sharing the same clinica.iotools module.

The base idea is to have:

  • the CLI clinica convert using code from the clinica.converters module
  • the CLI clinica iotools using code from the clinica.iotools module
  • the CLI clinica run using code from the clinica.pipelines module

Objects used in multiple modules are moved in another top-level module (at the moment it is clinica.utils although this may evolve to something better one day...).

This is in our roadmap as the first step toward maybe splitting the converters of Clinica into their separate package one day.

Things to do

  • Fix all the broken unit tests
  • Make sure non regression tests are passing
  • Make smaller architectural improvements (especially around things related to BIDS which are still defined in multiple places....)

@NicolasGensollen NicolasGensollen self-assigned this Feb 21, 2025
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

Successfully merging this pull request may close these issues.

1 participant