currentlyI'm working onthe resolutionof aMIPintegratinga moduleused to estimatthe reliability of thepower grid.When Iexecutemy modelwith the optionTimestepwithout the reliability moduleand conversely,everything works fine.However,when Iexcecutewith both, There area compilation error:*** Abort"COMPILEERRORSINGAMS**", followed by severalmessages**Did notfindGAMS...**
I guess itmust havea problem ofcompatibility between the two.I wonder ifanyone hasever hadthis kind of problem?
It could be some compatibility problem. Could you upload the run file and the listing file (*.LST) for the case with these errors (packed into a ZIP file), so that I could see what the problem is?
BTW: decided to delete the ZIP file from here, as you had used an option to include the full TIMES source code in the listing file.
I verified that the problem is not related to the TIMES code itself, but to your FIA extension, which is not correctly coded to be usable under the stepped mode. And, as ETSAP does not provide support for the proper GAMS coding of user extensions, it is basically your responsibility.
But I can give some quick advice: You should include the TIMESTEP controls directly in the equation headers (e.g. EQ_FIAOF(R,T,P,S)) and remove them from the code inside the equations.
I can also see that you are using a very old TIMES version (3.3.1). Note that TIMES support is basically always provided only for the latest versions.
As you included your full model in the listing file, I was able to test with the FIA extension myself under time-stepped mode. With just small corrections to the equ_ext.fia file, the model solved fine, both with TIMES v3.3.1 and the latest TIMES v3.8.6. Using OPTCR=0 the MIP solutions were also identical up to the second timestep (the third step took too much time with OPTCR=0 for me to wait for it to finish).
Therefore, I still don't see why you choose to use the old version. The modified equ_ext files for both versions are here: uploads/28/equ_ext-fias.zip
Hello, I haveaccessto only twoversions ofTIMES,3.0.2and3.3.1.this iswhyI work on 3.3.1.I tested themodel withchangesmadeit workvery well .Thankyouso muchfor your help.