Skip to content
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

Glmnet mex error on Windows 10 #3

Open
agitter opened this issue Jan 21, 2019 · 1 comment
Open

Glmnet mex error on Windows 10 #3

agitter opened this issue Jan 21, 2019 · 1 comment

Comments

@agitter
Copy link
Member

agitter commented Jan 21, 2019

Running SCINGE_Example on Windows 10 with MATLAB R2014b generated a system error: MATLAB has encountered an internal problem and needs to close.

The error details include the message Access violation detected. The first lines of the stack trace (with paths edited) are:

Stack Trace (from fault):
[  0] 0x00000000fe160b03 ...\MATLAB\R2014b\bin\win64\libmx.dll+00396035 MXGETPR+00000003
[  1] 0x00007ff879dc19dc ...\SCINGE\glmnet_matlab\glmnetMex.mexw64+00006620 MEXFUNCTION+00002524

Possibly related to these issues:

Re-compiling the Glmnet code may be the next step.

@agitter
Copy link
Member Author

agitter commented Feb 24, 2021

I tried running SINGE_Example on Windows 10 with MATLAB R2018a. It appears to run now. I'm still using the same version of glmnet_matlab I have from 2015 and did not recompile anything.

We should explore whether SINGE runs stably in Windows on newer versions of MATLAB.

Further testing shows that SINGE can run successfully in MATLAB R2018a on the example data (data1). The outputs match the reference outputs as well.

The aggregation step requires using Windows file separators \ in the path because of this line

lind = max(max(strfind(Str,filesep)),0);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant