Problem: Currently the benchmark feature added automatically shows us how many items were completed per minute during computationally intensive parts of the pipeline. When scripts take multiple days however, the arithmetic is incorrect, resulting in negative numbers for total computational time.
Solution: Adding days to the timestamp object creature for keeping track of benchmarking should solve the issue.
Problem: Currently the benchmark feature added automatically shows us how many items were completed per minute during computationally intensive parts of the pipeline. When scripts take multiple days however, the arithmetic is incorrect, resulting in negative numbers for total computational time.
Solution: Adding days to the timestamp object creature for keeping track of benchmarking should solve the issue.