-
Notifications
You must be signed in to change notification settings - Fork 29
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
ncore problem #11
Comments
This is weird because each cluster should load package biglasso and then package bigmemory (because it's a depends). As a new version of package bigmemory has just been released to CRAN it is worth reinstalling everything. Begin a new clean R session. Install package bigmemory then install package biglasso. |
Just reinstalled bigmemory and biglasso from cran. Having same problem |
Okay. Sorry, I have no computer to test/do this now. |
Thanks. Let me try. |
Now it is showing |
See this |
Thanks, let me take a look at it. Although I couldn't fixed the issue entirely. I kind of fixed it by changing parLapply part by mclapply as I figured that it was coming from passing functions. Forking shouldn't have this issues ideally. I committed the changes in my forked biglasso repo.
This would only work on mac/linux based R. Could you possibly test once you have a computer? |
Crashes outright on Windows 10. Installed from CRAN. R v3.5.3, biglasso 1.3-6. I also saw mention of "parLapply" above. That doesn't work on Windows either. A lot of Big Data companies use Windows... |
|
Thanks privelf, Apparently I have another problem causing the crash, or I was confusing it with the other parallel apply that doesn't work (it just uses 1 thread instead of all of them). Maybe I was thinking mclapply (lot of parallel interfaces!). What can I do to help debug? |
I don't understand your problem. |
My problem is a crash on simple data. I have opened an issue about it here: #22 Thanks for your help. |
Hi,
I am having some problem with the ncores option in biglasso() and cv.biglasso() function. I compiled biglasso on my mac enabling openMP (4 cores). However, when I am trying to reproduce the worked out example of the cv.biglasso() function usng ncores=4, I am getting an error
I got the same error in our cluster where biglasso is compiled using intel MKL. Can anyone help?
Thanks,
Subhomoy
The text was updated successfully, but these errors were encountered: