-
Notifications
You must be signed in to change notification settings - Fork 38
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
missing pairs - somalier relate v. >= 0.2.7 #76
Comments
Hi, I agree this is confusing, There is some randomness and that's why you see mildly different numbers between versions -- you'd also see this if you ran the same version multiple times. Let me know if this answers your question or if you have suggestions to make it less jarring. I suppose I could see the random number generator with a fixed number so you'd get identical results post v0.2.6. |
Hi, thank you for clarifying this. As I understood it, when the number of sample-pairs is above the cutoff, some pairings will be left out for the sake of the html plot. Is there a way to force somalier relate to write down all pairings to the pairs.tsv outupt file? Thanks |
Yes, I can probably make this a hidden option. Just to clarify, somalier will only skip writing pairs that are both:
all other pairs will be written. |
Hi Brent, I would like to follow up on this thread and ask if it would be possible to implement a silent option to output all pairings in the .group.tsv file, regardless of the 2 conditions written above (1. unrelated by genotypes 2. expected to be unrelated). It would be great if tis could be done in the latest version (0.2.13). Thanks :) |
Hi, this is available in the latest release by setting the environment variable |
I am running somalier -relate and compared the pairs.tsv output across different versions of somalier package.
The input to somalier relate is n=875 .somalier files, then the corresponding pairs.tsv output file should contain the relatedness between all possible pairings n=382.375 (no repetition, order does not count).
Yet, this is true only for some versions, and NOT for the latest (v 0.2.13):
The text was updated successfully, but these errors were encountered: