Modified _parse_gdx_results in GAMS.py to replace _parse_special_value and Updated Import Statement #3642
+41
−4
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.
Fixes #3624
Summary/Motivation:
When parsing the results of a model after it has been solved, the level and dual value are obtained through a series of
if
statements in_parse_special_values
that may cause slowdowns. This PR added GAMS existing functions to handle data parser for these special values in_parse_gdx_results
.Changes proposed in this PR:
_parse_special_values
with GAMS special value parser in_parse_gdx_results
.attempt_import
to have fallback to pre-GAMS-45.0 API ifgams.core.gdx
is not available.Legal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: