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
Currently, even if every output file of the main pipeline is not changed between multiple reruns, when we archive coverage maps, the archives themselves will be different in terms of their binary contents.
This is likely due to the fact that our archival program, tar, is capturing timestamps (ctime, mtime, atime) and stores them in the archive.
As the result, it is always true that Kive reports a change between reruns, even if they produced identical results.
For the fix, we should ensure that tar behaves time-independently.
The text was updated successfully, but these errors were encountered:
Another option is to deploy the next release of Kive, so we can have output directories, instead of only output files. That way, we won't need any tar or zip files.
I can't remember if we also had a problem with the PDF files' time stamps, or if we used a constant timestamp to avoid the problem.
Currently, even if every output file of the main pipeline is not changed between multiple reruns, when we archive coverage maps, the archives themselves will be different in terms of their binary contents.
This is likely due to the fact that our archival program, tar, is capturing timestamps (ctime, mtime, atime) and stores them in the archive.
As the result, it is always true that Kive reports a change between reruns, even if they produced identical results.
For the fix, we should ensure that
tar
behaves time-independently.The text was updated successfully, but these errors were encountered: