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
Evoquer: a BigQuery-based joint calling tool #6011
Open
droazen
wants to merge
3
commits into
master
Choose a base branch
from
dr_jts_lb_evoquer
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
from
June 24, 2019 18:52
3ec664f
to
9539a42
Compare
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
from
July 9, 2019 17:06
ac6b164
to
d3e265f
Compare
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
from
July 17, 2019 21:20
fd8342c
to
6a8dab0
Compare
Codecov Report
@@ Coverage Diff @@
## master #6011 +/- ##
=========================================
Coverage ? 7.002%
Complexity ? 2962
=========================================
Files ? 1998
Lines ? 150096
Branches ? 16654
=========================================
Hits ? 10509
Misses ? 138811
Partials ? 776
|
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
from
September 13, 2019 20:47
1b3bb25
to
01dc26e
Compare
I've rebased this branch and updated it to the latest |
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
4 times, most recently
from
October 17, 2019 20:17
0e19356
to
a67919b
Compare
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
2 times, most recently
from
November 7, 2019 13:53
fe652b1
to
cf7d02b
Compare
droazen
changed the title
Evoquer: the "group by" version (WIP -- DO NOT MERGE)
Evoquer: a BigQuery-based joint calling tool
Nov 7, 2019
Fix genotype allele remapping issue Set samplesAreUniquified = false in ref confidence merger to avoid sample name mangling Add a hack to skip sites with the wrong number of values in allele-specific annotations This is necessary to work with our current test datasets More robust hack to deal with malformed allele-specific annotations evoquer.sh improvements Handle missing values (".") in AS_QualByDepth Add additional VCF header line declarations required by the GnarlyGenotyper Avoid potential NPE in onShutdown() Update test dataset name Keep the NON_REF allele during merging when running the GnarlyGenotyper Comment out empty annotations in GnarlyGenotyper Updates to evoquer.wdl Add clarification about removal of NON_REF allele More evoquer.wdl updates Support raw precomputed AVRO inputs Add a --run-query-in-batch-mode argument More WDL updates Add WDLs Set PIPELINE_MAX_ALT_COUNT to 50 in the GnarlyGenotyper to work around an IndexOutOfBoundsException dalio run 2 WDL settings Switch to 'evoquer_dalio40k_july_updated_dataset_map' Replace USING with ON in the main query, and adjust WHERE clause for better query performance GnarlyGenotyperEngine: create GenotypeLikelihoodCalculators on-the-fly when there are too many alleles Add dalio WDL + supporting files to scripts/unsupported/evoquer Update WDL to use clustered versions of the dalio tables Remove old WDL directory to avoid potential confusion Revert "Replace USING with ON in the main query, and adjust WHERE clause for better query performance" This reverts commit 80e5140. Switch to the latest gatk/master version of the GnarlyGenotyper Switch back to shaded NIO classes added optimized query Andrea bug fix: don't reuse Avro records in Storage API evoquer integration tests Remove temporary seenPositions hack from the EvoquerEngine Fix some failing tests Fix post-rebase breakage fix for jackson dependency issue only update minicluster to 3+ updating to use hadoop3 everywhere adding NO_GCE_CHECK=true make tests cloudy make errors more verbose replace 2.11 with scalaVersion Update Evoquer integration test expected output Update to google-cloud-java 0.117.0 Don't hardcode the project ID in executeQueryWithStorageAPI() Update protobuf-java to 3.8.0 SortingCollection
droazen
force-pushed
the
dr_jts_lb_evoquer
branch
from
November 7, 2019 17:18
cf7d02b
to
dbd79f6
Compare
* fix bug in median calculation along with unit test * Parameterize table name to use for list of samples, and update query to only extract that list of samples. This adds a new capability of subsetting, but also fixes a bug where the unrestricted query extracted samples that were not in the sample_list and thus the inferred genotypes could be incorrect * Function to dry-run query in order to get the estimated bytes processed * fixed test case * revert changes for ExcessHet to match master * Disable CNNVariantPipelineTest.testTrainingReadModel until failures are resolved. (#6331) Co-authored-by: Andrea Haessly <ahaessly@broadinstitute.org> Co-authored-by: Chris Norman <cnorman@broadinstitute.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.