Dear list, Dirk and Professor J.C. Nash gave me an invaluable help! Prof. Nash mentioned:
> Possibly this is a quirk of the particular distro or machine, BLAS or > LAPACK[.] This was indeed the case, and Dirk's suggestion to > [install] libopenblas-openmp-dev" and > [remove] both "libopenblas-pthread-dev libopenblas0-pthread" immediately solved the problem! Before applying the fix, I took note of my /sessionInfo() /output: > > sessionInfo() > R version 3.6.3 (2020-02-29) > Platform: x86_64-pc-linux-gnu (64-bit) > Running under: Ubuntu 20.04 LTS > > Matrix products: default > BLAS: /usr/lib/x86_64-linux-gnu/openblas-pthread/libblas.so.3 > LAPACK: /usr/lib/x86_64-linux-gnu/openblas-pthread/liblapack.so.3 > > locale: > [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C > [3] LC_TIME=de_DE.UTF-8 LC_COLLATE=en_US.UTF-8 > [5] LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8 > [7] LC_PAPER=de_DE.UTF-8 LC_NAME=C > [9] LC_ADDRESS=C LC_TELEPHONE=C > [11] LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=C > > attached base packages: > [1] stats graphics grDevices utils datasets methods base > > loaded via a namespace (and not attached): > [1] compiler_3.6.3 *Is there anything that I can do, so that others** **do not experience the same issue?* Writing a bug report comes into my mind... In this last paragraph I append some information on my hardware, as Dirk suggested in his previous mail, as well as a summary of the software I'm using. > Operating System: Kubuntu 20.04 > KDE Plasma Version: 5.18.4 > KDE Frameworks Version: 5.68.0 > Qt Version: 5.12.8 > Kernel Version: 5.4.0-28-generic > OS Type: 64-bit > Processors: 8 × Intel® Core™ i5-8300H CPU @ 2.30GHz > Memory: 7,4 GiB of RAM Again, thanks for all the help! I really appreciate it. :) Byeongmin On 09.05.20 18:35, Dirk Eddelbuettel wrote: > On 9 May 2020 at 10:30, Dirk Eddelbuettel wrote: > | > | We can see that you use Linux. > | > | Are you by chance > | > | - on a Debian or Ubuntu system, and > | - have the libopenblas package installed ? > | > | If so then it is a known bug with the libopenblas0-pthread package. > | > | Installing libopen0-openmp (and also removing libopenblas0-pthread) should > | fix it. > > That was imprecise. It should read "installing libopenblas-openmp-dev" and > removing both "libopenblas-pthread-dev libopenblas0-pthread". > > I cannot reproduce the bug on the hardware I have access to (i5, i7, xeon) > though I was able to a few weeks ago. Maybe something changed already... > > There was also a brief thread on the debian-science list (within Debian) > starting with https://lists.debian.org/debian-science/2020/04/msg00081.html > and leading to https://lists.debian.org/debian-science/2020/05/msg00003.html > (and this cross from April to May) > > We would need some more information on hardware to chase this. > > Dirk > > | This is likely CPU dependent. But we need more info. Can you maybe come to > the > | r-sig-debian list (subscription needed to reduce spam) and we continue > there? > | > | Dirk > | > | > | -- > | http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > | > | ______________________________________________ > | R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see > | https://stat.ethz.ch/mailman/listinfo/r-help > | PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > | and provide commented, minimal, self-contained, reproducible code. > [[alternative HTML version deleted]] ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
