Open oesteban opened 3 years ago
Don't you prefer to go step by step with targeted PRs? We can deal with the CLI once we have a functional prototype.
Once again, the CLI is literally the last thing I would care for :D
The core of the component classification code in tedana is that each classification step is its own function. I don't think it's realistic to completely harmonize the two sets of classification codes now, but if you set it up so that each classification decision is modularized, it should be realistic to use the same system for both in the near future.
Ok guys, I've made the following changes:
write_metrics
has been moved to io.py
.classification.py
with a function for each criteria as @handwerkerd mentioned.What do you think @tsalo @cesarcaballerogaudes @oesteban?
Edit: no idea why the style check fails.
Closes # .
Changes proposed in this pull request:
-