GAMS World Forum

Hi, you can find more info in the documentation of GAMS 37. This is still a beta, find a link here: https://www.gams.com/beta/ The GAMS Transfer Matlab documentation is here: https://www.gams.com/37/docs/API_MATLAB_GAMSTRANSFER_OVERVIEW.html And the GAMS Transfer Python documentation is here: https:...

But this is because of the model and not the Matlab interface. In the model you reset the values before you solve: R_m$(ord(t)=1) = 0; Q_m$(ord(t)=1) = 0; R_m =4; R_p=1*R(t); Q_m =4; Q_p=1*Q(t); Remove the above and change execute_load 'gams_matlab.gdx'; to execute_load 'gams_matlab.gdx' Q_m, Q_p, R...

Hi, your wgdx input structures are incorrect. If you don't provide the field "type", it is assumed "set". And if you don't set "form" to "full" you can't pass a single value as it is assumed "sparse". In sparse format you have to provide a n+1 column...

There actually is a workaround: Instead of using 0 as value try something very small and ideally smaller than CPLEX's tolerance epint, e.g. 1e-8. Note that you also have to set tryint to that value (or something bigger).

This turns out to be a bug (and I can't think of a workaround). It will be fixed with the next GAMS release. Thanks very much for reporting!