Closed dlakaplan closed 1 year ago
Plus relevant data to reconstruct actions.
What keyword should we use for the git hash?
I would probably just put it in the history - that's where ASKAPsoft stores version information and also where I've stored the cropping information.
For the selavy files we need a keyword because they don't have a generic history parameter. I guess something like vastPostProcessingVersion
(subject to whatever we decide to rename the repo to).
Closed by #36.
Add code at the end of correction to add git hash to a new header.