-
Notifications
You must be signed in to change notification settings - Fork 67
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
VPhaser output intepretation - strand bias p value #789
Comments
The documentation for V-Phaser II can be found here:
V-Phaser II was developed before my time at the Broad, so for methodological questions I'll point you to the original paper (10.1186/1471-2164-14-674), but perhaps @dpark01 can chime in. It does apply Benjamini-Hochberg correction, so perhaps that could explain the difference you're seeing in p-value. |
Thanks a lot Chris! Am I correct in interpreting the above as ~ 37% chance of strand bias is the first row and ~ 75% chance of strand bias in the second row ? |
Also @tomkinsc would you recommend I rather use intrahost.py in the viral-ngs package ? (as I see it seems to achieve the same functionality) |
Hello
I have three questions pertaining to the VPhaser output
Pos Var Cons Strd_bias_pval Type Var_perc SNP_or_LP_Profile
1425 A T 0.3718 snp 0.3173 A:3:3 C:3:1 G:1:1 T:1319:560
1426 A G 0.756 snp 0.2629 A:2:3 G:1332:561 T:1:3
Specifically, How is it that I get such different p values for such a close allelic diversity profile ?
In my limited understanding I interpret a 0.7 strand bias p value to be higher evidence of strand bias and 0.37 to be poor evidence of strand bias, but it seems difficult to explain with such close allele counts (I did try a 2*2 Fishers Test with the above values, but got different results for p value...wondering it its because VPhaser does BH correction.)
What does var_perc in the output mean ?
I am assuming file.nofdr.var.txt is the file that has both the strand bias corrections and fdr corrections.. please correct me if I am wrong
The text was updated successfully, but these errors were encountered: