-
Notifications
You must be signed in to change notification settings - Fork 23
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
Wildcards in group subsetting? #164
Comments
Hi Phil, |
Matter of fact it does.
But problem here is I have to know the names of each clone, as opposed to a more generalized "clone" label. Just curious if there is any such operation as clone.each or clone.any or clone.all when referring back to a sample from the column titled "clone". If not I can keep it hard coded in the pipeline...such is the challenge of pipeline flexibility to differing inputs. If no such operation exists it's a bummer and you can close the thread...it's been tough to move away from GEMINI in python2...and I'm missing operations like https://gemini.readthedocs.io/en/latest/content/querying.html#gt-filter-wildcard-filtering-on-genotype-columns Thanks for a great tool though! |
I see. I think you can use:
that expression probably doesn't do anything useful, but shows how you'd use I'm still confused about exactly what you want to do. usually you'd have:
then ancesors and clones will both be javascript arrays (because column ends in 's'. |
Question not bug:
Can you select wildcards for subsetting across samples for a genotype?
My use case:
Single ancestor line, multiple clones derived from it. Alias file:
Code chunk with subset expression:
If I want any clone.AD[1] >= value; or all clone.AD[1] is that possible with the --group-expr function?
One workaround could be changing the alias file to
and expanding the group expression to
But that requires that || (or) is implemented in your subsetting code.
Any advice?
Thanks,
Phil
For example, I want to access AD[1] or DP acro
The text was updated successfully, but these errors were encountered: