-
Notifications
You must be signed in to change notification settings - Fork 95
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] Remove accepted and rejected outputs #822
Conversation
Also remove the term "optcom" from certain outputs.
I still need to change which maps are required for the reports, but are we happy with the output changes overall? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good overall.
@@ -27,25 +27,9 @@ | |||
"orig": "betas_OC", | |||
"bidsv1.5.0": "desc-ICA_stat-z_components" | |||
}, | |||
"ICA accepted components img": { | |||
"orig": "betas_hik_OC", | |||
"bidsv1.5.0": "desc-ICAAccepted_components" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the first place we should add a new file name version code? That is we are changing file names and preventing people from saving files with these older names. We can rename the current ones something like "bidsv1.5.0old". While I don't think anyone would want to use these older names, the big benefit is, if someone has files with these old names, they'd/we'd be able to quickly remember what they now correspond to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BIDS is on v1.6.0 right now, so I'd lean toward adding that and changing the default over renaming v1.5.0. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I now realize that we should have done something like this for #736 as well... and we should probably have our different versions reflected in the outputs tables too!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aligning with v1.6.0 with this PR sounds sounds like a great solution.
Did #736 change any file names or just change what was in some of the files? If it changed a file name, I could see back-adding that into the output filename table, but this seems really minor. I'd say don't bother or consider it a really low priority.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It changed the T2* and S0 maps. T2starmap.nii.gz --> desc-limited_T2starmap.nii.gz and desc-full_T2starmap.nii.gz --> T2starmap.nii.gz.
One caveat: I don't believe any of our changes are driven by changes to the specification. Our 1.5.0 names should be completely compatible with 1.6.0, and vice versa. It's just a useful way to version our own names without adding in entirely new elements to the naming convention. Well, it's useful as long as we don't make major changes to our naming convention faster than BIDS releases, I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beyond adding the v1.6.0 naming convention (and reverting name changes, but not removals, from v1.5.0) in 280771c, here's what I'm thinking could help:
Unfortunately, this would involve working through our commit history to pin down when each filename was changed and which tedana versions the changes apply to, which I don't want to tackle in this PR, but I think the overall idea is solid.
EDIT: Or I guess meica.py - v0.0.10 instead of Original filename
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest just opening a new issue for adding in the intermediate file naming convention.
FWIW, when we made this file naming decision, I think we talked about creating new file naming options that were linked to a released version. That is, we'd always be able to say "Save files as they were in tedana v0.0.9" I don't see that in the current code, but this discussion shows why such an option might be useful. Whatever we call each naming convention, there would also be an ordered list saying in which version each convention was the default. This wouldn't be too hard to add, but it would definitely be a new issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@handwerkerd that is correct, I proposed that if this becomes an issue we could alias a few tedana versions to certain naming conventions (not track them in the JSON file itself).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logical place to do this would be in the input parser in the init of io.OutputGenerator
The one quirk is that would mean every time we edit outputs.json, we'd also want to add to the parser to peg the current version with the previous file names.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #822 +/- ##
==========================================
+ Coverage 88.91% 93.20% +4.28%
==========================================
Files 27 27
Lines 3375 2193 -1182
Branches 618 0 -618
==========================================
- Hits 3001 2044 -957
+ Misses 227 149 -78
+ Partials 147 0 -147
☔ View full report in Codecov by Sentry. |
I believe we decided recently that it would be easier to just start over from scratch on this instead of trying to fix up the PR. |
Closes #819.
Changes proposed in this pull request:
n_vols
parameter fromio.writeresults
.docs/outputs.rst
.Removed derivatives
Renamed derivatives
To do: