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
RELAX empty files in results, and results differing when re-run #1685
Comments
Dear @lmnano,
Convergence Checks and Reporting.RELAX does two convergence checks. 1). Flat likelihood surface. After the alternative model is fitted, HyPhy will do a grid sample (varying If K was inferred to be > 1, the optimization will be done FORCING K ≤ 1 (and vice verse). If this results in a better LogL, analysis will be labeled as unstable. 2). If a negative LRT (null vs full) is encountered, this will trigger a refit and a warning. Console output will look like this
In the JSON file look for “convernce-*” keys in the analysis/settings object path Best, |
Dear Sergei, Thank you for a detailed answer. |
Dear @lmnano, Please let me know how it goes. Best, |
Dear Sergei, This took a bit longer than expected. For now we're still getting empty files in the results. As for differing results, I need to find some time to check. I will let you know about that as well. |
Dear @lmnano, Do you have any error/message log details for the runs that fail? How are you scheduling these jobs? Best, |
Dear Sergei, It took me a while to get back to this. First regarding empty files. Currently we have an analysis that has between 16 and 22 vertebrate species in each alignment. The data is split by number of species in the alignments. In this analysis there are between 76 and 1623 alignments for each number of species. RELAX is run on a Linux workstation in command line from a bash script that makes a list of all the alignments for a certain number of species in the analysis and runs RELAX for each one separately in a for loop. Each RELAX run is a consecutive instance of this for loop. There is no scheduler on the workstation, the script is run as a background job. The machine should be powerful enough to run this without any issues. I have re-run RELAX for all of the results that came up empty and they produced results, although some had to be re-run twice. I have log files for each run, two different errors seem to occur. Since every log file covers all of the alignments in one run and is therefore very long, I copy-pasted only the part that is relevant to one of the alignments that produced an empty result and put it in the attachments, one for each kind of error: Second the reproducibility issue. I tested this more thoroughly by randomly selecting 100 alignments from one of the sets and re-running RELAX on them. One of them returned an empty file, which I discarded. I compared the rest with the previous results and the resulting selection type inferred from test results (relaxed, intensified or none) differed for about 15 % of the alignments. I used your suggested settings from a previous post in both runs. Also, is there a way to test for consistency or convergence of the tested parameters in Hyphy? |
Stale issue message |
Hi
We're currently using RELAX in analyses across 16-32 vertebrate species and I noticed some issues with the results.
First for a bit of context, we're running RELAX on multiple gene alignments. It is run using a bash script that takes all the individual gene alignments in a specific folder and runs RELAX for each alignment in a for loop. There are two problems occurring in the results:
An example example of differing test results (relaxation parameter in this example):
Original run:
Re-run:
I also completely re-ran (using the for loop) one of the shorter analysis, the only difference being the output folder. Some of the results were inconsistent. In the second run there were no empty files among the results and some numbers also differed.
My questions are, how to know which results are the right ones, and why are we getting empty files and different results?
The text was updated successfully, but these errors were encountered: