Adding python library version numbers #1014
Merged
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.
When we closed #747 I had made a comment that we might also want to log the version numbers of key modules used by tedana. This PR does that (plus identifies & corrects an omission from that PR)
Changes proposed in this pull request:
dataset_description.json
includes the version numbers for all libraries specified inproject.toml
utils.get_system_info
is nowutils.get_system_and_version_info
. The previous line to get the python version was moved from tedana.py and ica_reclassify.py into this function and this function now compiles the version numbers for the other packagestedana
andica_reclassify
workflows saves the system information, butt2smap
did not so I added that info tot2smap
_main
functions for getting the text of a command line input worked for an actual command line input, but nottedana_cli
calls, which we were using in the tests. I think I fixed this is a way that won't break anything else.tedana_report.html
via edits toreport_info_table_template.html
andhtml_report.py
For future work (or edits to this PR). The three work flows all have a very similar block of text to specify and write
derivative_metadata
This could be it's own function. Also,BIDSVersion
is hard-coded in all three. Given 1.5.0 is the only version we support, that's not a big deal, but, if we ever add an updated output option, we might want to make that a variable.I was reminded to do this via nipreps/fmriprep#3196