[ENH] Separate converters and iotools in separate modules #1443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
clinica convert
using code from theclinica.converters
moduleclinica iotools
using code from theclinica.iotools
moduleclinica run
using code from theclinica.pipelines
moduleObjects 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