BEAST 1.10.4 can't find BEAGLE on Mac

238 views
Skip to first unread message

Wolfgang Wüster

unread,
Feb 23, 2023, 12:14:49 PM2/23/23
to beast-users
I am trying to run BEAST 1.10.4 on a Macbook running OS Ventura 13.2, and cannot get it to find BEAGLE, whether v. 4.0.0 (current) or the older 3.1.0. I would really appreciate any help in resolving this.

Many thanks in anticipation,

Wolfgang


Mike Lee

unread,
Aug 28, 2023, 2:59:11 AM8/28/23
to beast-users
This worked for me, thank Marc

Marc Suchard
Aug 25, 2022, 1:44:19 AM
to beast-users
To the best of my understanding, these are not issues with BEAGLE.   BEAGLE v4 on Mac is now a universal build that supports x86 and ARM64 execution automatically.  Rather, the issues seem to be related to Apple changing the default search paths on M1 systems when executing BEAST through the GUI application.    I have found a patch that works and expect to provide an updated BEAST release relatively soon.   In the meantime, here's how one can make the patch on their local computer:

1. Open in Finder the directory that contains the BEAST v1.10.4.app
2. Control-click to Show Package Contents
3. Open in a text editor Info.plist
4. Change this line:
       <string>-Xmx2048M</string>
   to now read
        <string>-Xmx2048M -Djava.library.path=/usr/local/lib</string>
5. Save and re-execute BEAST v1.10.4.app

As far as I can tell, these issues do not arise when using the command-line script `beast` since that script already adds the necessary java.library.path VM option.

best, Marc

Claire Schraidt

unread,
Nov 1, 2023, 3:04:55 PM11/1/23
to beast-users
How did you manage to modify the Info.plist file? I can't edit it and haven't been able to change the read write permissions on the disk.

Pfeiffer, Wayne

unread,
Nov 1, 2023, 7:53:13 PM11/1/23
to beast...@googlegroups.com, Pfeiffer, Wayne
Hi Marc,

There is still a problem that goes beyond the issue with running on Macs.

In August and September last year we exchanged email in which I reported that BEAST 1.10.4 with BEAGLE 4.0.0 does not achieve parallel speedup on x86 cores because the beagle_thread_count option does not work properly in BEAST. You confirmed this and made a fix to BEAST 1.10.5.prerelease but did not provide one for 1.10.4, which is what we support via the CIPRES gateway since we are reluctant to use prerelease software.

Will you provide a fix soon that works with either 1.10.4 or a new official release of 1.10.5?

Wayne

-- 
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/77f6fb1d-721b-4311-9ce7-18047e897d98n%40googlegroups.com.

Reply all
Reply to author
Forward
0 new messages