Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seasnap-mapping does not run for some in path configurations #29

Open
january3 opened this issue Nov 17, 2023 · 1 comment
Open

seasnap-mapping does not run for some in path configurations #29

january3 opened this issue Nov 17, 2023 · 1 comment

Comments

@january3
Copy link
Member

Fastq files were stored according to the following pattern:

input/{sample}/fastq/{sample}{lane}{mate}

seasnap-mapping with this configuration did not correctly run - the file
argument was empty for fastqc and star.

@bobermayer
Copy link
Contributor

can confirm with pattern input/{sample}/fastq/{sample}_S*_{lane}_{mate}_*.
at least for star and fastqc, I think it's because there's no all_lanes flag as (e.g.,) in rule ciri
patrick has a # TODO: case of ignored wildcards? meant for e.g. allFlowcell in get_fastq_pairs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants