Closed nsheff closed 3 weeks ago
I see where this went wrong and will add a partial fix shortly.
Basically, we changed pipestat's item access behavior last fall.
psm[_pipeline_name]
should change to psm.pipeline_name
What is Destroyer currently doing? For each sample, the destroy function will check the sample output folder, e.g. `results/results_pipeline/frog_1' and destroy that folder. It will not touch the submission folder.
It will not destroy the results.yaml
created by pipestat. Thus, currently, selecting a specific sample will not remove it from the results.yaml
file.
Destroyer goes on to call destroy_summary: It appears as though the destroy_summary function only destroys the summary files:
To that point, we should make sure it will also destroy the aggregate_results.yaml
produced when running results to multiple results files (e.g. currently how PEPATAC operates).
Also, there do not appear to be any tests for Destroyer functionality. So, it makes sense that this broke without us knowing.
results.yaml
aggregate_results.yaml
I've implemented the fix for this with the above merged PR.
Can't looper destroy something.
Related to #459. and also #464 -- these things should have been caught by testing.