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

NIO output support for HaplotypeCaller #4721

Merged
merged 2 commits into from
May 22, 2018
Merged

NIO output support for HaplotypeCaller #4721

merged 2 commits into from
May 22, 2018

Conversation

jean-philippe-martin
Copy link
Contributor

@jean-philippe-martin jean-philippe-martin commented Apr 30, 2018

HaplotypeCaller's bamOutputPath is no longer internally converted to a File so "gs://" paths can now be passed for the optional "bam output" parameter.

@codecov-io
Copy link

codecov-io commented Apr 30, 2018

Codecov Report

Merging #4721 into master will not change coverage.
The diff coverage is 100%.

@@             Coverage Diff             @@
##              master     #4721   +/-   ##
===========================================
  Coverage     80.124%   80.124%           
  Complexity     17436     17436           
===========================================
  Files           1082      1082           
  Lines          63150     63150           
  Branches       10187     10187           
===========================================
  Hits           50598     50598           
  Misses          8568      8568           
  Partials        3984      3984
Impacted Files Coverage Δ Complexity Δ
...hellbender/utils/haplotype/SAMFileDestination.java 100% <ø> (ø) 3 <0> (ø) ⬇️
...hellbender/utils/haplotype/HaplotypeBAMWriter.java 98.077% <100%> (ø) 10 <0> (ø) ⬇️
...kers/haplotypecaller/AssemblyBasedCallerUtils.java 70.297% <100%> (ø) 25 <0> (ø) ⬇️

@jean-philippe-martin
Copy link
Contributor Author

@droazen this is ready for review!

@jean-philippe-martin
Copy link
Contributor Author

ping? It's been a little while, a review would be nice. If @droazen is busy, perhaps @lbergelson can have a look?

@droazen droazen self-requested a review May 9, 2018 19:19
@droazen
Copy link
Contributor

droazen commented May 9, 2018

@jean-philippe-martin I'll try to get to this one this week

@droazen droazen requested review from jamesemery and removed request for droazen May 14, 2018 19:13
@droazen droazen assigned jamesemery and unassigned droazen May 14, 2018
Copy link
Collaborator

@jamesemery jamesemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs a test

@@ -10,6 +10,7 @@
import htsjdk.samtools.util.Locatable;
import htsjdk.samtools.SamFiles;

import java.nio.file.Path;
Copy link
Collaborator

@jamesemery jamesemery May 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add a test (either here or in HaplotypeCallerIntegrationTest which asserts that the tool can actually write into the test bucket (similar to the ApplyBQSRIntegrationTest.testApplyBQSRCloud() test you wrote for a one of your other branches).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I added it to HaplotypeCallerIntegrationTest, in the "bucket" group.

Copy link
Collaborator

@jamesemery jamesemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test looks good 👍. It looks like you have a merge conflict, i'm going to go ahead and fix that quickly and merge

@jamesemery jamesemery force-pushed the jp_haplotype_path branch from 8f1c977 to bccb477 Compare May 21, 2018 19:46
@jean-philippe-martin
Copy link
Contributor Author

Awesome, @jamesemery, thank you very much!

@jamesemery jamesemery merged commit 06a5050 into master May 22, 2018
@jean-philippe-martin jean-philippe-martin deleted the jp_haplotype_path branch May 23, 2018 17:35
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

Successfully merging this pull request may close these issues.

4 participants