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
Data 10 presents with the metadata problem if BCF is chosen as the output along with "uncompressed" set (uncompressed does not change to compressed when BCF is chosen instead of VCF). Is there a reason why this option is on the tool form? Couldn't it be hidden from the user? Choosing VCF implies uncompressed already, and BCF compressed. The user shouldn't need to specify this twice -- it leaves open an easy way to create a problematic output. If BCF/compressed are both set, the job is successful (Data 13).
Warnings in all outputs. Looks like the tool needs an update anyway. Maybe can add in the above at the next rev?
[warning] tag DPR functional, but deprecated. Please switch to `AD` in future.
[warning] tag DV functional, but deprecated. Please switch to `AD` in future.
[warning] tag DP4 functional, but deprecated. Please switch to `ADF` and `ADR` in future.
[warning] tag INFO/DPR functional, but deprecated. Please switch to `INFO/AD` in future.
[mpileup] 1 samples in 1 input files
<mpileup> Set max per-file depth to 8000
In samtools 1.9 cvf/bcf output has been deprecated and I have removed it in #1973 from the galaxy tool. Users should use bcftools. If those are available and functional we could close the issue.
This will need some dev input for main (usegalaxy.org). Deprecating tools is a bit complicated there. I'll create a distinct tracking ticket this week around the issue/solution and close this one out then.
MTS: https://toolshed.g2.bx.psu.edu/view/devteam/samtools_mpileup/583abf29fc8e
Test history: https://usegalaxy.org/u/jen/h/test-history-mpileup-bcftools-call
Data 10 presents with the metadata problem if BCF is chosen as the output along with "uncompressed" set (uncompressed does not change to compressed when BCF is chosen instead of VCF). Is there a reason why this option is on the tool form? Couldn't it be hidden from the user? Choosing VCF implies uncompressed already, and BCF compressed. The user shouldn't need to specify this twice -- it leaves open an easy way to create a problematic output. If BCF/compressed are both set, the job is successful (Data 13).
Warnings in all outputs. Looks like the tool needs an update anyway. Maybe can add in the above at the next rev?
Found during testing for galaxyproject/usegalaxy-playbook#123
Update for
.org
tracked here: galaxyproject/usegalaxy-playbook#133The text was updated successfully, but these errors were encountered: