Snakemake report statistics error
Snakemake report fails when the jobs are running in the cluster. The running times appear to be 0.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- BIOPZ-Katsantoni Maria changed milestone to %downstream
changed milestone to %downstream
- BIOPZ-Katsantoni Maria added Bug label
added Bug label
- BIOPZ-Katsantoni Maria added downstream label
added downstream label
- BIOPZ-Katsantoni Maria assigned to @gypas
assigned to @gypas
- Author Maintainer
Check the version of snakemake that is used. This is most probably because of the module that creates the report.
- BIOPZ-Katsantoni Maria added To Do label
added To Do label
- BIOPZ-Gypas Foivos added Doing label and removed To Do label
- Maintainer
This is not the case anymore. I attach a screenshot showing that when you roll over the rule it displays the time in seconds. The result you get both with local and slurm execution.
@katsanto I think we can close this.
Collapse replies - Author Maintainer
I think I agree with @bakma on this.. if all running times are so low why are the differences not visible? Is there a hardcoded cutoff on the running time?
- Maintainer
I will make a test run with a real dataset to check.
- Maintainer
Isn't this a bit suspicious that all rules are at the initial line? Or is this an artifact of of a small dummy input, maybe?
- BIOPZ-Gypas Foivos mentioned in issue #179 (closed)
mentioned in issue #179 (closed)
- Maintainer
So far my conclusion is that it displays the waiting time in the queue and not the actual run time. See also an open issue here: https://github.com/snakemake/snakemake/issues/517
When running locally it calculates the correct time, but it displays all the results on the same y-axis.
I am testing with a newer version of snakemake, to see if this is fixed.
Edited by BIOPZ-Gypas Foivos 1 1 - Author Maintainer
Check if this is fixed in the newest snakemake version otherwise drop completely.
- Owner
I wouldn't drop this completely, we can just document and point to the issue on Snakemake. Once it's fixed and we upgrade to the corresponding Snakemake version, we'll benefit immediately. Plus even now it should be fully function for local execution and possibly at least very slightly functional/informative for cluster execution (perhaps might even work for clusters other than Slurm?)
1 - Maintainer
It seems that
6.5.3
fixes this. I will test with6.5.5
as well, because6.5.3
introduced another problem when we run the tests.Edited by BIOPZ-Gypas Foivos Collapse replies - Maintainer
Once it runs through - could you also post a screenshot here?
1 - Maintainer
- Maintainer
- Maintainer
OK, seems this is working fine in the new Snakemake; so a PR for here would be a version bump?
- Maintainer
Yes, I am running another test locally and then I will open a PR.
1
- BIOPZ-Gypas Foivos mentioned in merge request !95 (merged)
mentioned in merge request !95 (merged)
- Maintainer
Fixed in !95 (merged)
- BIOPZ-Gypas Foivos closed
closed