Open soininen opened 3 weeks ago
gamsapi may also be used without using gams itself or the gdx files that are created with gamsapi are used with older gams (should be compatible). So, I think it's not necessary to check for the GAMS installation version - we wouldn't know the users intent.
The old dgxcc
package did require a GAMS installation so I thought it would be the same with the compatibility layer of gamsapi
. Looks like I have been wrong all along. This simplifies things a lot as it allow us to drop the requirement of GAMS installation (and the knowledge of GAMS dir) from Exporter and Importer.
I misunderstood the situation. The legacy functionality in gamsapi
that we use in Importer/Exporter does require a GAMS installation. This should not force users to specific GAMS version in their Tools, though. I guess the solution would be to allow users to set a different GAMS for Importer/Exporter in settings.
Settings should have two boxes:
Then in tool spec one can choose which to use. The first one can also be checked for version (at least GAMS 42).
We switched from
dgxcc
togamsapi
some time ago. I finally figured out the oldest GAMS version that supportsgamsapi
and it is 42. We should upgrade the note inCHANGELOG.md
(for version 0.8.4). If possible, we should also check and warn user if their GAMS installation is too old in "proper places" (find_gams_directory()
?).