Skip to content

[FileFormats.MPS] fix parsing of OBJSENSE #2016

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 15, 2022
Merged

[FileFormats.MPS] fix parsing of OBJSENSE #2016

merged 1 commit into from
Oct 15, 2022

Conversation

odow
Copy link
Member

@odow odow commented Oct 14, 2022

Closes #2015

@odow odow added Type: Bug Submodule: FileFormats About the FileFormats submodule labels Oct 14, 2022
@odow odow merged commit d364d1d into master Oct 15, 2022
@odow odow deleted the od/fix-mps-objsense branch October 15, 2022 09:25
@matbesancon
Copy link
Contributor

So apparently, the optional sense is a section so it could even make sense to write it on two separate lines and not one
https://www.ibm.com/docs/en/icos/22.1.0?topic=extensions-objective-sense-name-offset-in-mps-files

@odow
Copy link
Member Author

odow commented Oct 17, 2022

Gurobi has it on one line: https://www.gurobi.com/documentation/9.5/refman/mps_format.html 😄

But some testing shows that it looks like Gurobi can read from the next line, so perhaps I will change the writing.

@odow odow mentioned this pull request Oct 17, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@matbesancon matbesancon matbesancon approved these changes

Assignees
No one assigned
Labels
Submodule: FileFormats About the FileFormats submodule Type: Bug
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

FileFormats.MPS OBJSENSE
2 participants
@odow @matbesancon