-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issues with run (see log panel below) - no error message. #144
Comments
Hi, |
Hi, I ran into a similar error as described above, only I cannot find an error in the log but I also don't have a reftable.log file. only the diyabc_run_call.log file. |
Hi, I'm runnig standalone wep app on windows 10. Thanks in advance! Lican |
I found the problem here! #124 (comment) |
Hi, I am really sorry for the very late reply. Due to work overload, the development, support and maintenance for the project diyabcGUI is currently paused. Feel free to contact us (by submitting an issue) if you want to take over the development for this project. Pull request are also welcome to fix bug or implement missing functionalities. I have updated the README file to announce this. This is the official announcement to clarify a situation that has been going on for quite some time. You can still use the command line version of the software which is still maintained/supported. Check the documentation page here. All my apologies for the trouble, |
Hi,
I'm trying to run a single simply scenario to test DIYABC-RF. I have attached the log file.
diyabc_run_call.log
I am running the shiny R gui on Mac OS X Ventura 13.0.1. I installed following the instructions here: https://diyabc.github.io/gui/
Here is the headerRF.txt:
headerRF.txt
The reftableRF.bin files is not saving, despite it seeming to complete in the log - perhaps this is the issue?
Is there another place I should be looking for the error message?
Thanks,
Miranda
EDIT; I've just seen an error message in the reftable.log : A gene genealogy failed in scenario 1. Check consistency of this scenario over possible prior ranges of time event parameters.
The text was updated successfully, but these errors were encountered: