Description
Talking with R2R folks, they'd like to be able to capture a snapshot of what parameters, device definitions, configurations, etc are running during a cruise. This could be done with a script, either manually invoked, or somehow automatically invoked when something is changed, that captures the cruise definition file, all of the device definitions it's calling in, and the branch/version/timestamp of the OpenRVDAS code being run.
Script would package/pickle/tar the information into an easily storable file that could be archived with the data produced on a cruise. Note that because some definitions refer to/include other definitions, the script would have to read and traverse the relevant directories.
Bonus functionality would be for it to (periodically?) do a diff and save a new timestamped copy if any of the relevant files have changed.