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

check_options possible invalid options combination #28

Open
talassio opened this issue Apr 2, 2019 · 0 comments
Open

check_options possible invalid options combination #28

talassio opened this issue Apr 2, 2019 · 0 comments

Comments

@talassio
Copy link
Collaborator

talassio commented Apr 2, 2019

Need to make sure regularization_solve is NOT called with opt%reg_order /= 2.
We should catch the specific combination of options that triggers this "not yet supported" combination before entering the solver, at the
check_options() phase.

This can be difficult, given that the regularization parameter can be changed dynamically internally, and this can change between steps (although only if a regularization parameter less than zero was sent in the first call). i.e., it's the value of this in the workspace that's important.

The checking of options opt%type_of_method==2 .And. opt%nlls_method==3 are certainly required.

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

No branches or pull requests

2 participants