Take into account discreteness for no cost zero variables in bounds section #2299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that there was inconsistency in https://github.com/ERGO-Code/HiGHS/blob/master/src/io/HMPSIO.cpp#L879 with https://github.com/ERGO-Code/HiGHS/blob/master/src/io/HMPSIO.cpp#L724-L728
As I understand, for example, https://github.com/ERGO-Code/HiGHS/blob/master/src/io/HMPSIO.cpp#L925-L927 - for no cost zero integer variable with
lb = 0
andub = +inf
LI BOUND
will be written (unlesswrite_no_cost_zero_columns = false
) and then maybe it is worth taking this into account innum_no_cost_zero_columns_in_bounds_section
variable and corresponding log