-
Notifications
You must be signed in to change notification settings - Fork 24
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
Binary vs Integer Variables #169
Comments
With the default mesh and direction type used by Nomad, binary variables are converted into integer variables (granularity 1) with 0 and 1 bounds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the variables in my optimization problem are all binary, is there any difference internally to NOMAD between specifying them as binary by setting BB_INPUT_TYPE to (B B B) versus specifying them as integers by setting BB_INPUT_TYPE to (I I I) with lower bounds 0 and upper bounds 1? For example, does specifying them explicitly as binary using the first approach realize computational and/or memory efficiencies for NOMAD?
The text was updated successfully, but these errors were encountered: