search

MikkelSchubert / paleomix

Pipelines and tools for the processing of ancient and modern HTS data.
https://paleomix.readthedocs.io/en/stable/
MIT License
43 stars 19 forks source link

time elapsed reset by using function keys #9

Closed ginolhac closed 7 years ago

ginolhac commented 8 years ago

In v1.2.5 in the screen output, the time elapsed is updated, a feature I like: 14:02:34 Running 3 tasks using ~3 of max 6 threads; 143 done of 166 tasks in 2:03s

after using l to list (or increasing / decreasing # cores to use), the elapsed time is reset

14:11:11 Running 3 tasks using ~3 of max 6 threads; 143 done of 166 tasks in 0s

would it be possible to leave this time counter aside from using keys?

MikkelSchubert commented 8 years ago

This is a bug in the reporting code, but it should only happen when you use the 'l' command, since that creates a temporary progress reporter, and it should not affect the running time reported for subsequent status updates, including when changing threads. Can you check if this is the case? Otherwise there's another bug I am missing.

Regardless, I'll add a fix for this in the next version of PALEOMIX.

ginolhac commented 8 years ago

I can confirm the final reported time is correct. Actually, when the progress reporter is updated by paleomix it became correct again 14:34:44 Running 3 tasks using ~3 of max 6 threads; 160 done of 166 tasks in 34:13s

So, yes it is only when the refresh is manually activated