Skip to content

Feature counts for paired end reads #10

@Fred-White94

Description

@Fred-White94

Despite there being the function to determine from the sample file whether or not you have single or paired end reads this does not carry over to the featurecounts rule which is only set up for single end (and fails to properly count the reads for paired end samples).

The use of -p option for paired end reads should be linked to the initial function. Easiest way would be to add in another if else for this rule with and without the -p. I cannot think of a way to include it with minimal code (i.e. avoiding another if else).

You could make the sample_is_single_end output a wildcard {endedness} which ="" for single ended and = "-p" for paired end?

Cheers!

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