-
Notifications
You must be signed in to change notification settings - Fork 1
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
Extension loading issue while running LPhyBEAST 1.1.0 via cmd #152
Comments
The error message shows the class In the meantime, you can try to uninstall phylonco using In addition, this problem does not relate to the LPhyBeastExt package, so I transfer it to here. |
It seems the current released version of The problem is that phylonco package is not compatible to the lphybeast. The lphybeast core has no issue. |
@CSTE7007 We have released the new version of LPhy 1.6.0 and LPhyBEAST 1.2.0, and phylonco 1.2.0, phylonco.lphybeast 1.2.0. This problem will be solved if you update them to those new versions. In this new version, phylonco is split into 2 releases, one (phylonco) is for BEAST 2 only, the other (phylonco.lphybeast ) is for LPhyBEAST to create XML. The dependency detail is listed in the new user manual. We are updating the rest webpages at the moment. Please note : if you are using phylonco lphy or phylonco lphybeast, please remember to put the two jar files (phylonco-lphy and phylonco-lphy-studio ) into LPhy lib folder, and remove the old one. Thank you to support our software. |
I will keep this issue open for 2 weeks, if any problems, please ask here. |
I was trying to follow LPhyBEAST mentioned at the usage section at https://linguaphylo.github.io/setup/
I copied the lphybeast file to my beast/bin directory
and then in my terminal I wrote
./lphybeast ~/lphy-studio-1.5.0/tutorials/RSV2.lphy
The lphybeast script would have generate the “RSV2.xml”
But instead I am facing the following exception and error:
My configuration:
BEAST v2.7.7
Ubuntu 18.04.6 LTS 64-bit | 8GB RAM
Intel® Core™ i5-3470 CPU @ 3.20GHz × 4
The text was updated successfully, but these errors were encountered: