Skip to content
This repository has been archived by the owner on Mar 17, 2023. It is now read-only.

Test single vs paired end bam files #18

Open
olgabot opened this issue Mar 3, 2020 · 0 comments
Open

Test single vs paired end bam files #18

olgabot opened this issue Mar 3, 2020 · 0 comments

Comments

@olgabot
Copy link
Contributor

olgabot commented Mar 3, 2020

  1. Add a test configuration using this single-end bam and bai file:
  1. Add a bamPaths parameter to nextflow.config like readPaths for testing

  2. Update the bam file parsing as in Support input of multiple bam files with --bam '*{.bam,.bam.bai}' #19 (maybe not necessary, but would make downstream stuff easier)

  3. Update the samtools_view_fastq process to (approximately):

	output:
	set val(interval_name), file("*.fastq.gz") into ch_intersected

if (params.paired_end) {
"""
samtools view -hu $bam '${chrom}:${chromStart}-${chromEnd}' \\
  | samtools fastq -N -1 ${interval_name}_R1.fastq.gz -2 ${interval_name)_R2.fastq.gz
} else {
  samtools view -hu $bam '${chrom}:${chromStart}-${chromEnd}' \\
		| samtools fastq -N - \\
		| gzip -c > ${interval_name}.fastq.gz
}
  1. Make sure tests pass! :)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant