Skip to content

sorted bams still accepted when unsorted or qname sorted bams specified #11012

@gnaisha

Description

@gnaisha

I'm trying to fix the eXpress and Salmon wrappers to accept qname.sorted bams or unsorted bams, since these tools explicitly require random (coordinate) sort order for their alignment inputs. However, even when removing the "bam" type input, sorted bams are populated in the drop down and accepted as valid input. Could this behavior be changed to disallow sorted bams as input when either unsorted or qname.sorted bams are specified?

Here is the issue that sparked this concern galaxyproject/tools-devteam#581 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions