Avatar

registered_user

  • Total activity 31
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 7

Activity overview

Latest activity by registered_user
  • Avatar

    registered_user commented,

    Hi Pamela Bretscher, yes I think so. Thanks.

  • Avatar

    registered_user commented,

    Solution: gatk --java-options "-Dsamjdk.compression_level=6" ApplyBQSR [options]

  • Avatar

    registered_user commented,

    I was able to get a ~25% filesize reduction with running the bam file through samtools view. However, trying to use "ApplyBQSR --java-options "-Dsamjdk.compression_level=6" results in error: Error:...

  • Avatar

    registered_user commented,

    This might work:  samtools view -@ 6 -h -b --output-fmt-option level=6 -o compressed.bam uncompressed.bqsr.bam You should be able to leave out "--output-fmt-option level=6" and it should work just ...

  • Avatar

    registered_user created a post,

    ApplyBQSR wastes too much disk space

    I have made the mistake of using the default compression level for ApplyBQSR and now I have terabytes of wasted space in my project bam files. The recalibrated files take up twice the disk space in...

  • Avatar

    registered_user commented,

    Compression level 2 effectively doubles the file size. I would be interested to know what kind of speed advantage are we talking about here to outweigh this massive waste of disk space. The BQSR pr...

  • Avatar

    registered_user created a post,

    LeftAlignAndTrimVariants removes header tags

    I noticed that LeftAlignAndTrimVariants (GATK 4.1.8.1) keeps only the first entry of normal- and tumor sample header tags in VCF files. This is unexpected and unwanted behavior. Trimming should not...

  • Avatar

    registered_user commented,

    Thanks for the explanation. For cancer heterogeneity analysis, this is the exact opposite functionality that is required. I think SelectVariants should have some option to remove undetected variant...

  • Avatar

    registered_user commented,

    Nope... this still leaves in variants like: GT:AD:AF:DP:F1R2:F2R1:SB 0/1:52,0:0.019:52:26,0:26,0:35,17,0,0 I think there might be a bug somewhere in Mutect that sets the GT field erroneously to "0/1".

  • Avatar

    registered_user commented,

    Having "##fileformat=VCFv4.2" at the beginning of the --alleles .vcf.gz file seems to have done the trick.