You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As commented by @yarikoptic in nipreps/fmriprep#1802 (comment), it would be great to implement in the client some utility to keep track of the exact template used in an analysis.
I guess that the actual git commit of the templateflow/templateflow repo should suffice? WDYT?
The text was updated successfully, but these errors were encountered:
if you do not expect all files to change with every commit, and do not want to refetch all of them upon each upgrade -- might be overkill. But if that is ok, then might be better to may be use git describe (well, git describe --tags since I guess releases are done via github and release tags aren't annotated) version for a given commit? then it would be a clear version for releases and then smth like 1.2.1-4-g350b8b9 if somehow current development version was used? then besides the commit hexsha (350b8b9) you would get the release as well
oesteban
changed the title
Guaranteeing the exact version of a template used
Reporting the exact version of a template used
Jul 5, 2021
As commented by @yarikoptic in nipreps/fmriprep#1802 (comment), it would be great to implement in the client some utility to keep track of the exact template used in an analysis.
I guess that the actual git commit of the templateflow/templateflow repo should suffice? WDYT?
The text was updated successfully, but these errors were encountered: