Skip to content
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

The problem of parsing RELAX results #31

Open
1221li opened this issue Dec 30, 2022 · 1 comment
Open

The problem of parsing RELAX results #31

1221li opened this issue Dec 30, 2022 · 1 comment

Comments

@1221li
Copy link

1221li commented Dec 30, 2022

Dear Developer,

Thank you very much for developing such a useful software, which has provided me with great help. But I have some doubts about how to interpret this result.

If I have nine species, and I use one of the lineages as the "TEST" for the RELAX analysis. I'm going to get the json result, which has the K value for each species and node, and if I understand all right, a "relaxation or intensification parameter", which seems to be the final K value. My question is, should I use the final K value or can I also use the k value for each species and node. Whether the results of labeling multiple species as TEST differ substantially from those of labeling a single species as TEST.

Looking forward to your reply!

1672390165354

@spond
Copy link
Member

spond commented Dec 31, 2022

Dear @1221li,

In your actual example, the p-value for the test is not significant (p~0.4), hence K is not significantly different from 1.

RELAX will fit several models and each may have different K estimates. Which one you use depends on your application. The standard use of RELAX is to report the overall K value (test vs reference), but only if the p-value shows a significant result.

Best,
Sergei

PS. Consider loading the JSON into the RELAX visualization module at vision.hyphy.org/RELAX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants