Closed malachig closed 10 years ago
One thing that is strange about the output above is the warning:
2014-03-12 00:59:59-0500 clia1: Removing sites supported by less than callers
The number of callers required should be defined there via $self->required_snv_callers
. This has a default defined in both Genome/Model/SomaticVariation.pm
and Genome/Model/SomaticVariation/Command/CreateReport.pm
.
One thing I noticed that may be a red herring is that parameters in the class defs for these modules are using a mix of default => x
and default_value => x
required_snv_callers is a new processing profile parameter. The reason that the default in the tool doesn't kick in is because the workflow passes that parameter in from the processing profile. In the in-house Genome instance, we backfilled all of the processing profiles to have the default value. To fix the immediate error, you could backfill the processing profiles in sGMS as well.
Handling these types of release migrations given multiple instances of Genome is a much larger topic.
there are two more parameters beside required_snv_callers that need to be backfilled: tiers_to_review and restrict_to_target_regions. All of them can be backfilled with the default value of 1.
I think a new metadata dump for the sGMS will help backfill these processing profiles on the sGMS.
Yes, testing that now.
The new metadata dump is here: https://xfer.genome.wustl.edu/gxfer1/project/gms/testdata/GMS1/export/18177dd5eca44514a47f367d9804e17a-2014.3.12.dat
No problems importing it and running new ref-align builds. Testing somatic-variation now to see if the issue is resolved
Somatic-variation processing profiles have now been updated and somatic-variation builds are once again succeeding. Closing this issue now.
Since the merge we are getting warnings and errors in somatic-variation create-report step summarized below:
First,
And then later,
It looks like all of this was added recently by @susannasiebert. We should confer with her before proceeding further.