Veda2.0 Released!


Trade processes not being defined
#1
Hello guys,
I am trying to run a model with around 10 different regions
I have set the files for trade link and trade parameters with all the connection required, but when I am receiving several warning messages that my parameters haven't been defined yet (below a few).
I am attaching the lst files and the trade files too, do you know what I am doing wrongly?
Thanks!!!

1810  BOL.2012.TU_GASMT_BOL_BRN_01.UP 57
****    $170                    $170
**** LINE    16 BATINCLUDE  C:\VEDA\VEDA_FE\GAMS_WRKTIMES\tradeparameters.dd
**** LINE    54 INPUT      C:\VEDA\VEDA_FE\GAMS_WRKTIMES\Test_20210609.RUN
1811  BRN.2012.TU_GASMT_BOL_BRN_01.UP 57
****    $170                    $170
**** LINE    17 BATINCLUDE  C:\VEDA\VEDA_FE\GAMS_WRKTIMES\tradeparameters.dd
**** LINE    54 INPUT      C:\VEDA\VEDA_FE\GAMS_WRKTIMES\Test_20210609.RUN
1812  BOL.2013.TU_GASMT_BOL_BRN_01.UP 57
****    $170                    $170
**** LINE    18 BATINCLUDE  C:\VEDA\VEDA_FE\GAMS_WRKTIMES\tradeparameters.dd
**** LINE    54 INPUT      C:\VEDA\VEDA_FE\GAMS_WRKTIMES\Test_20210609.RUN
1813  BRN.2013.TU_GASMT_BOL_BRN_01.UP 57
****    $170                    $170


Attached Files
.xls   ScenTrade__Trade_Links.XLS (Size: 31 KB / Downloads: 1)
.xls   ScenTrade_TRADEPARAMETERS.xls (Size: 815.5 KB / Downloads: 2)
.txt   Test_20210609.txt (Size: 633.87 KB / Downloads: 2)
Reply
#2
TIMES does not see BOL and BRN defined as regions. Post a screenshot of your Model root folder (to check the VT file names) and upload SysSettings.
Reply
#3
Hi Amit,
Thanks for helping.
I am attaching both


Attached Files Thumbnail(s)
   

.xls   SysSettings.xls (Size: 119 KB / Downloads: 2)
Reply
#4
Looking at the listing file reveals the problem: The tradeparameters scenario is written out (and read by GAMS) before the Base scenario, where the regions are defined:

    15    1794 BATINCLUDE    1      54  .C:\VEDA\VEDA_FE\GAMS_WRKTIMES\tradeparameters.dd
    16    3524 BATINCLUDE    1      55  .C:\VEDA\VEDA_FE\GAMS_WRKTIMES\base.dd
    17  194156 BATINCLUDE    1      56  .C:\VEDA\VEDA_FE\GAMS_WRKTIMES\syssettings.dd

You can easily correct for that, by moving the tradeparameters scenario below Base in the Case Manager, Scenarios list box.
Reply
#5
Hi Antti,
Thank you for the support. I did this change and had no warning messages!

Thanks a lot guys for taking the time to support!
Reply
#6
Hi guys,
Sorry bothering you again, but after that previous error, I am receiving this error message below
Do you know what is the cause for such error?
Thanks!!!

**** Exec Error at line 213784: Equation infeasible due to rhs value

**** INFEASIBLE EQUATIONS ...

---- EQL_CPT  =L=  Capacity Transfer (=L=)

EQL_CPT(ARS,2019,TB_GASMARKET_ARE_ARS_01)..  0 =L= -5.6843418860808E-14 ; (LHS = 0, INFES = 5.6843418860808E-14 ****)
   
EQL_CPT(ARS,2020,TB_GASMARKET_ARE_ARS_01)..  0 =L= -5.6843418860808E-14 ; (LHS = 0, INFES = 5.6843418860808E-14 ****)


Attached Files
.txt   Test_20210609_Run_Log.txt (Size: 225.16 KB / Downloads: 1)
Reply
#7
GAMS detects some tiny infeasibilities in your model.
You are defining both PRC_RESID=X and CAP_BND(FX)=X for many trade processes.  That is somewhat error-prone, because the numerical accuracy is limited.  In your case, the CAP_BND(FX)=X appears to be in two cases a tiny bit lower than PRC_RESID=X (~10^-14).

I would suggest that instead of defining CAP_BND(FX)=X, where X is meant to be equal to the existing capacity, you should define NCAP_BND(FX)=0.  Then you should be able to avoid those tiny infeasibilities.
Reply
#8
Thank you, Antti, that stopped the issue!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)