-
Notifications
You must be signed in to change notification settings - Fork 69
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
Contrast-FEL results interpretation in hyphy #1780
Comments
Dear @geofrunz, Sorry for the delay is responding. As you've discovered, the documentation page is rather old, and no longer matches what the When you run the 'overall' test, e.g., a branch-set vs the rest of the tree,
When two specific groups are being compared, their order is reported and the For the example from the documentation,
If you look at the Which tell you how to interpert the values in the following record. For example at codon 4
Hope this helps, |
Dear Sergei, Thank you so much for your reply! Now I understand! I used Vision.hyphy to visualize the JSON file, and I assume I get the same results — the foreground beta and background beta values in the appropriate columns, correct? I just marked the foreground branches. Thank you so much again. Very best regards, |
Dear @geofrunz, That's correct. You should be able to see a breakdown by branch-set in vision. Best, |
Dear all,
Sorry for the basic question. I am trying to use Contrast-FEL in HyPhy for better annotation of the tree branches. However, when I get the results, I cannot figure out in which dataset beta is greater.
I tried using the reference dataset provided in https://hyphy.org/methods/other/contrast-fel/, and while the values match, in the local version the larger values are always reported in the right-hand column, regardless of whether they refer to the test or reference dataset.
this is different compared to the table provided in the tutorial (https://hyphy.org/methods/other/contrast-fel/)
Is there a way to clarify this?
I'm using HYPHY 2.5.64(MP)
Thank you in advance!
The text was updated successfully, but these errors were encountered: