We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/scottclowe/matlab-continuous-integration provides an example of Travis CI testing for MATLAB code via Octave. If we can run SCINGE on Octave, we can set up basic continuous integration testing.
This would likely require recompiling or adapting the Glmnet mex files for Octave.
The text was updated successfully, but these errors were encountered:
It may be easiest to test SCINGE inside and Octave Docker container such as:
There are instructions and examples for setting up Travis CI with Docker:
Step 1 would be to enable Travis CI on this repository. Then we can do all the testing in a new pull request.
Sorry, something went wrong.
Because we found that MATLAB can run within Docker, that may be a faster route to setting up Travis CI. An example is https://hub.docker.com/r/fbenz/docker-java-matlab
This should be fixed in Octave 4.4 per this bug report https://savannah.gnu.org/bugs/?func=detailitem&item_id=53951
No branches or pull requests
https://github.com/scottclowe/matlab-continuous-integration provides an example of Travis CI testing for MATLAB code via Octave. If we can run SCINGE on Octave, we can set up basic continuous integration testing.
This would likely require recompiling or adapting the Glmnet mex files for Octave.
The text was updated successfully, but these errors were encountered: