Skip to content

Build in some sort readmapping parsing #51

@halexand

Description

@halexand

The mega merge file appears has a lot of contigs that don't recruit reads in other samples. While this is probably okay at some level of the analysis, when it comes to comparing counts / coverage across samples it probably makes sense to try to work with a subset of transcripts that are relatively well covered across samples.

Maybe implement a cut that looks at initial salmon mapping and requires a transcript to have a count > 0 in X % of samples or the like?

I am also curious how this ultimately impacts read recruitment against megamerge.

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