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

LongReads: remove unmapped bams #247

Open
6 of 8 tasks
leonschuetz opened this issue Feb 8, 2024 · 5 comments
Open
6 of 8 tasks

LongReads: remove unmapped bams #247

leonschuetz opened this issue Feb 8, 2024 · 5 comments

Comments

@leonschuetz
Copy link
Collaborator

leonschuetz commented Feb 8, 2024

  • fix bug in mapping pipeline:

    • reads are lost during mapping
    • determine step and fix
  • add check for sufficient file size/read count in mapped BAM

  • remove unmapped BAM according to project setting

  • add CRAM support:

    • check if cram can be used for downsteam analysis
    • if not: implement code to unpack it on-the-fly
@leonschuetz
Copy link
Collaborator Author

  • integrate new longphase version
    • should be fixed in 1.7.2

@leonschuetz
Copy link
Collaborator Author

  • cram corrupted after Calling -> longphase?

@leonschuetz
Copy link
Collaborator Author

  • samtools reports 0 reads for whole chrs, but section contain reads
  • also some times after mapping
  • can be solved by resorting the file (not only re-writing)
  • test mapping seperately

@leonschuetz
Copy link
Collaborator Author

  • test special CRAM options for methylation

@leonschuetz
Copy link
Collaborator Author

  • tests on HG001/HG002: 0/5 reads missing
    • all reads are duplicates in original bam file (re-base called?)
  • test on set of diagnostic samples
  • add function to check BAMs (chr-wise)
  • add checks at each point on which the BAM/CRAM is modified

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

1 participant