You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
Looking at the oncotator files issued from firebrowse, the validation alleles can be listed as . or - when there are no samples for it to validate with. Huge problem, as one cannot tell if the allele is a "-" (gap) or if it simply does not have data available. See LUAD vs KIRC.
The text was updated successfully, but these errors were encountered:
this sounds like a question for GDAC or the firebrowse team. Oncotator is
simply rendering what was provided by the analyst.
On Nov 16, 2015 12:19 PM, "Ryan-Singh" notifications@github.com wrote:
Looking at the oncotator files issued from firebrowse, the validation
alleles can be listed as . or - when there are no samples for it to
validate with. Huge problem, as one cannot tell if the allele is a "-"
(gap) or if it simply does not have data available. See LUAD vs KIRC.
—
Reply to this email directly or view it on GitHub #336.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looking at the oncotator files issued from firebrowse, the validation alleles can be listed as . or - when there are no samples for it to validate with. Huge problem, as one cannot tell if the allele is a "-" (gap) or if it simply does not have data available. See LUAD vs KIRC.
The text was updated successfully, but these errors were encountered: