Bug#1025953: beast-mcmc: only usable with OpenCL
Hi Pierre, On 2022-12-12 22:51, Pierre Gruet wrote: Control: forwarded -1 https://github.com/CompEvol/beast2/issues/1069 [snip] It turns out I am meeting the same issue on beast2-mcmc (although not when typing only $ beast2-mcmc -help) and I am currently in touch with upstream for some packaging issues. I just opened the issue referenced on top of this email to get some help, which will also help for beast-mcmc. Thanks for forwarding. Such issues are indeed best solved upstream. Best, Andrius
Bug#1025953: beast-mcmc: only usable with OpenCL
Control: forwarded -1 https://github.com/CompEvol/beast2/issues/1069 Hi, Le 12/12/2022 à 17:08, Andreas Tille a écrit : Hi Andrius, Am Mon, Dec 12, 2022 at 04:06:40PM +0200 schrieb Andrius Merkys: When launched on a system without OpenCL, beast-mcmc executable dies: $ beast-mcmc -help OpenCL error: CL_DEVICE_NOT_FOUND from file , line 122. From a quick glance this seems to be happening due to beast-mcmc using OpenCL version of libhmsbeagle1v5 (the line cited in the error message is in libhmsbeagle source). However, beast-mcmc seems to support CLI options to switch to libhmsbeagle1v5 CPU instance (see 'beagle_CPU' in src/dr/app/beast/BeastMain.java). Maybe it is possible to make CPU mode the default to avoid loading OpenCL-dependent libraries. Thanks a lot for the hint. I've tried -beagle_CPU which fails and even -beagle_off[1] which fails as well[2]. Any hint would be welcome It turns out I am meeting the same issue on beast2-mcmc (although not when typing only $ beast2-mcmc -help) and I am currently in touch with upstream for some packaging issues. I just opened the issue referenced on top of this email to get some help, which will also help for beast-mcmc. Andreas. [1] https://salsa.debian.org/med-team/beast-mcmc/-/blob/master/debian/tests/run-unit-test#L12-13 [2] https://salsa.debian.org/med-team/beast-mcmc/-/jobs/3648046#L367 Best regards, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Bug#1025953: beast-mcmc: only usable with OpenCL
Hi Andreas, On 2022-12-12 18:08, Andreas Tille wrote: Am Mon, Dec 12, 2022 at 04:06:40PM +0200 schrieb Andrius Merkys: When launched on a system without OpenCL, beast-mcmc executable dies: $ beast-mcmc -help OpenCL error: CL_DEVICE_NOT_FOUND from file , line 122. From a quick glance this seems to be happening due to beast-mcmc using OpenCL version of libhmsbeagle1v5 (the line cited in the error message is in libhmsbeagle source). However, beast-mcmc seems to support CLI options to switch to libhmsbeagle1v5 CPU instance (see 'beagle_CPU' in src/dr/app/beast/BeastMain.java). Maybe it is possible to make CPU mode the default to avoid loading OpenCL-dependent libraries. Thanks a lot for the hint. I've tried -beagle_CPU which fails and even -beagle_off[1] which fails as well[2]. It looks as if beast-mcmc loads all shared libraries of libhmsbeagle unconditionally before parsing the CLI options. Or it sees that OpenCL headers are present (they are present even if no OpenCL device is available) and loads the OpenCL-dependent libraries. I did not dig into the source very much, though. Best, Andrius
Bug#1025953: beast-mcmc: only usable with OpenCL
Hi Andrius, Am Mon, Dec 12, 2022 at 04:06:40PM +0200 schrieb Andrius Merkys: > When launched on a system without OpenCL, beast-mcmc executable dies: > > $ beast-mcmc -help > OpenCL error: CL_DEVICE_NOT_FOUND from file , line > 122. > > From a quick glance this seems to be happening due to beast-mcmc using > OpenCL version of libhmsbeagle1v5 (the line cited in the error message is in > libhmsbeagle source). However, beast-mcmc seems to support CLI options to > switch to libhmsbeagle1v5 CPU instance (see 'beagle_CPU' in > src/dr/app/beast/BeastMain.java). Maybe it is possible to make CPU mode the > default to avoid loading OpenCL-dependent libraries. Thanks a lot for the hint. I've tried -beagle_CPU which fails and even -beagle_off[1] which fails as well[2]. Any hint would be welcome Andreas. [1] https://salsa.debian.org/med-team/beast-mcmc/-/blob/master/debian/tests/run-unit-test#L12-13 [2] https://salsa.debian.org/med-team/beast-mcmc/-/jobs/3648046#L367 -- http://fam-tille.de
Bug#1025953: beast-mcmc: only usable with OpenCL
Package: beast-mcmc Version: 1.10.4+dfsg-5 Severity: important Control: block 1025424 by -1 Hello, When launched on a system without OpenCL, beast-mcmc executable dies: $ beast-mcmc -help OpenCL error: CL_DEVICE_NOT_FOUND from file , line 122. From a quick glance this seems to be happening due to beast-mcmc using OpenCL version of libhmsbeagle1v5 (the line cited in the error message is in libhmsbeagle source). However, beast-mcmc seems to support CLI options to switch to libhmsbeagle1v5 CPU instance (see 'beagle_CPU' in src/dr/app/beast/BeastMain.java). Maybe it is possible to make CPU mode the default to avoid loading OpenCL-dependent libraries. Andrius
