beast terminate with error

461 views
Skip to first unread message

Rebecca Bengtsson

unread,
Sep 6, 2019, 2:28:36 PM9/6/19
to beast-users

Hi all,

 

I am running beast to perform divergence dating. I am working with microbial genomic data and have provided core genome SNPs alignment into beauti. To account for ascertainment bias I have also provided invariant sites in the xml file. When I run beast the following error occurs and my run is terminanted.

 

 

 

Start likelihood: -378.1335540171007

Warning: Overwriting file /Users/rjbeng/Documents/Shigella/data/flexneri/beast/subsample/flexneri_beast.log

         Sample      posterior     likelihood          prior

              0      -378.1335            NaN      -378.1335 --

Fatal exception: n must be positive

Warning: Overwriting file /Users/rjbeng/Documents/Shigella/data/flexneri/beast/subsample/flex_beast.trees

java.lang.IllegalArgumentException: n must be positive

            at beast.util.MersenneTwisterFast.nextInt(Unknown Source)

            at beast.util.Randomizer.nextInt(Unknown Source)

            at beast.evolution.operators.UniformOperator.proposal(Unknown Source)

            at beast.core.Operator.proposal(Unknown Source)

            at beast.core.MCMC.propagateState(Unknown Source)

            at beast.core.MCMC.doLoop(Unknown Source)

            at beast.core.MCMC.run(Unknown Source)

            at beast.app.BeastMCMC.run(Unknown Source)

            at beast.app.beastapp.BeastMain.<init>(Unknown Source)

            at beast.app.beastapp.BeastMain.main(Unknown Source)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

            at java.lang.reflect.Method.invoke(Method.java:498)

            at beast.app.beastapp.BeastLauncher.run(Unknown Source)

            at beast.app.beastapp.BeastLauncher.main(Unknown Source)

Fatal exception: n must be positive

 

BEAST has terminated with an error. Please select QUIT from the menu.


I have also performed the same analysis with sampling from prior and beast seems to run okay. I am not sure what is happening and would greatly appreciate some help.

 

I have attached the log output file

 

Many thanks

Rebecca

flexneri_beast.log

HS

unread,
Sep 7, 2019, 8:31:34 AM9/7/19
to beast-users
Hi Rebecca,

It is clear that likelihood can't be NaN. But to find out why the likelihood is NaN you should provide more info. Maybe it is good to share the priors tab of beauty or the priors part of xml file.

Best,
Hovhannes

Danushka Weerasekera

unread,
Sep 7, 2019, 2:49:14 PM9/7/19
to beast...@googlegroups.com
still its appearing an error massage

--
You received this message because you are subscribed to the Google Groups "beast-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beast-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beast-users/7df7c46b-7a8e-4db0-9322-01fed985eec3%40googlegroups.com.
deer nexx.nexus

Remco Bouckaert

unread,
Sep 8, 2019, 3:57:38 PM9/8/19
to beast...@googlegroups.com
Hi Lucy,

The error message suggests the a UniformOperator has a parameter with zero dimension, which should never happen and suggests perhaps something went wrong when setting up constant sites. 

The log file you posted shows the model, but has not likelihood in it which suggests the log was for a sample from the prior (and the likelihood will be NaN when sampling from the prior). 

If you can make the XML available, I can investigate further.

Cheers,

Remco


Remco Bouckaert

unread,
Sep 8, 2019, 4:20:24 PM9/8/19
to beast...@googlegroups.com
Hi Danushka,

Can you give more details on what seems to be the problem? I can import the alignment you posted and run it with a HKY model, strict clock and Yule prior (as in the attached) without any issues.

Remco

deer.xml

Rebecca Bengtsson

unread,
Sep 9, 2019, 4:50:43 AM9/9/19
to beast-users
Hi Hovhannes, 

I have managed to solve the issue by simply restarting beauti, entering all the information again and saving to a new xml file. I think the issue may have been caused by the fact that whenever I reopen a xml file in beauti the alignment file appears to be missing from the partitions window. I have no idea why this is happening, but restarting everything (inputing exactly the same priors) from scratch appears to solve the problem.

Many thanks
Rebecca 
Reply all
Reply to author
Forward
0 new messages