-
Notifications
You must be signed in to change notification settings - Fork 120
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
Genotype filter using wildcard with gt_alt_freqs > 0.3 #925
Comments
Anyone? |
When you say it did not work, do you mean you know for certain there are such variants and none were returned? |
Hi Aaron, Here is what I did and what the error message was: And the error message was: I think it is related to the "." in (>=0.3) since it complians about the number of elements. |
I encountered the same issue. It issues the "ValueError: Wildcard filter should consist of 4 elements" Also #868 is the same issue. |
This can be fixed by changing the file ....../python2.7/site-packages/gemini/GeminiQuery.py Line 1043: Line 1048: I have no idea if this breaks other functionalities, so make a backup of the original file. |
Dear gemini team,
I use gemini very frequently and it is an awesome tool for variant prioritization within large databases. However, one thing I could not find out yet is how to use the gt.alt.freqs option in combination with a wildcard.
For instance, I want all variants with impact severity MED or HIGH and with at least two affected individuals in our database:
gemini query --header -q "SELECT gene, chrom, start, end FROM variants where impact_severity != 'LOW'" --gt-filter "(gt_types).(Phenotype==2).(==HET).(count >1) and (gt_types).(Phenotype==1).(==HOM_REF).(all)" gemini.db
However, some of the identified variants have a very low gt.alt.freqs. How can I include a threshold for gt.alt.freqs for the identified variants? I tried : (gt_alt_freqs).(*).(>=0.3).(any), but it did not work.
Thank you very much for your help.
Oskar
The text was updated successfully, but these errors were encountered: