-
Notifications
You must be signed in to change notification settings - Fork 83
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
Issue related to javafx #1180
Comments
From the error message, it does not look like a JavaFX problem. Judging from the code, I think it appears to be looking for the path separator character, but finds an empty string. What OS are you running this on? |
Hello I run on archlinux, a linux distribution |
I'm even thinking, because we use the shared library, our de facto command is
but the official compiled package would be like this (I replace the path to our jar etc)
if we run the official command, it will report error, that's why we add some additional arg
Even I change the parameter
If I add -doNotRun true, it won't give error report |
Archlinux should return ":" as path separator. It maybe something to do with the actual XML: for path sampling in the Some unrelated question: are you performing a species delimitation analysis? If so, have you considered using speedemon instead? It usually is less painful than doing path sampling analysis (see blog post). |
I somewhat know why, it is supposed to run the beast2 after generating these heaps of beast.xml files and folders. But it only use default path, however, we may use different path, that's why? |
Perhaps this is the reason: for path sampling, each step directory has a script for running beast2.
Note that the script here has various parts replaced (everything of the form |
Yeah, thanks, that's all reasons I believed. Some unrelated words: thanks for your recommendation for another pkg, for our dataset… runing 48 steps path sampler to test 3 prior each model hypothesis is quite heavily computing tasks. 3 million nchain will run about 12h using beast. But for speedemon we don't have any prior, Epsilon is quite hard to estimate, I guess bayesian factor is not suitable for our current dataset based on limited knowledge and computing resources |
Glad to hear that fixed the problem. For epsilon, the blog post has a section on "Selecting the threshold ε", which may be useful for your analysis. |
Thanks for your response, I now close the issue |
I use the complied version from bioarchlinux maintained by me and @sukanka
But I found when I install some pkgs from beast2 beauti package management, for example, model_selection.
Then I run the command
Is that the problem that we compiled beast2 using java 23 openjfx etc?
The text was updated successfully, but these errors were encountered: