Veda2.0 Released!


Unexpected Termination of Run
#1
Unfortunately for some reason the EPAUS9rT model stopped solving again on the server computer. I'm not sure why since I have not changed any settings. I tried starting from scratch but I keep getting "Unexpected termination of run" error message. I looked at the GAMS_WRKTIMES code and it looks like something might be wrong with GAMS but I'm not sure how to diagnose the error (see below). Do you have any suggestions?

Thank you,

mike


*

*********************************************************************
*                                                                   *
*                            VEDA-TIMES                             *
*                     ========================                      *
*                                                                   *
*********************************************************************
*
--- Job EPAUS9rT_16_1_2ELCTax.RUN Start 02/23/18 23:44:14 24.7.4 r58773 WEX-WEI
x86 64bit/MS Windows
GAMS 24.7.4   Copyright © 1987-2016 GAMS Development. All rights reserved
Licensee: Engineering and Public Policy                  G160610:1121AO-GEN
          Carnegie Mellon University, Single Machine - 1 socket     DC10857
          License for teaching and research at degree granting institutions
          License Admin: Paulina Jaramillo, pjaramil@andrew.cmu.edu
--- Starting continued compilation
--- Workfile was generated under GAMS version WIN223-146
--- EPAUS9rT_16_1_2ELCTax.RUN(46) 2 Mb
--- .epaus9rt_16_1_2elctax_ts.dd(24) 3 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(51) 3 Mb
--- .initsys.mod(176) 3 Mb
--- ..units.def(14) 3 Mb
--- .initsys.mod(179) 3 Mb
--- ..maplists.def(116) 3 Mb
--- .initsys.mod(182) 3 Mb
--- ..globals.def(12) 3 Mb
--- .initsys.mod(182) 3 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(54) 3 Mb
--- .initmty.mod(726) 3 Mb
--- ..main_ext.mod(17) 3 Mb
--- ...initmty.DSC(13) 3 Mb
--- ..main_ext.mod(17) 3 Mb
--- ...initmty.VDA(59) 3 Mb
--- ..main_ext.mod(15) 3 Mb
--- .initmty.mod(728) 3 Mb
--- ..err_stat.mod(58) 3 Mb
--- .initmty.mod(729) 3 Mb
--- ..err_stat.mod(58) 3 Mb
--- .initmty.mod(735) 3 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(58) 3 Mb
--- .base.dd(1017206) 41 Mb 2 Errors
--- EPAUS9rT_16_1_2ELCTax.RUN(59) 41 Mb
--- .tradeparams.dd(756) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(60) 41 Mb
--- .syssettings.dd(56612) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(61) 41 Mb
--- .baseextra-offeps.dd(13) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(62) 41 Mb
--- .growth.dd(26166) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(63) 41 Mb
--- .uc-biofuelssimple.dd(1028) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(64) 41 Mb
--- .uc-elc.dd(7981) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(65) 41 Mb
--- .uc-rnw.dd(3970) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(66) 41 Mb
--- .uc-buildings.dd(13614) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(67) 41 Mb
--- .uc_trnhdv.dd(9663) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(68) 41 Mb
--- .uc_trnldv.dd(7643) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(69) 41 Mb
--- .uc-ind.dd(58310) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(70) 41 Mb
--- .aqreg.dd(63) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(71) 41 Mb
--- .uc_aqreg.dd(356) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(72) 41 Mb
--- .csapr-mats.dd(124) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(73) 41 Mb
--- .uc-csapr-mats.dd(455) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(74) 41 Mb
--- .elcco2tax.dd(396) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(83) 41 Mb
--- .maindrv.mod(18) 41 Mb
--- ..setglobs.gms(44) 41 Mb
--- .maindrv.mod(35) 41 Mb
***
*** Abort "*** ERRORS IN INPUT DATA/COMPILE ***"
--- .maindrv.mod(35) 41 Mb
--- EPAUS9rT_16_1_2ELCTax.RUN(83) 41 Mb
--- GDX File C:\VEDA\VEDA_FE\GAMS_WRKTIMES\GAMSSAVE\EPAUS9rT_16_1_2ELCTax.gdx
--- EPAUS9rT_16_1_2ELCTax.RUN(83) 41 Mb 3 Errors
*** Status: Compilation error(s)
--- Job EPAUS9rT_16_1_2ELCTax.RUN Stop 02/23/18 23:44:19 elapsed 0:00:05.386
--- GDX File : Symbols=575 UELs=9881
--- VEDA Cube: Dimensions=8 Entries=61 Text=3 SubSets=26
*** Did not find GAMS name par_actl in GDX file
*** Did not find GAMS name par_actm in GDX file
*** Did not find GAMS name par_capl in GDX file
*** Did not find GAMS name par_pasti in GDX file
*** Did not find GAMS name par_capm in GDX file
*** Did not find GAMS name par_ncapl in GDX file
*** Did not find GAMS name par_ncapm in GDX file
*** Did not find GAMS name par_ncapr in GDX file
*** Did not find GAMS name f_in in GDX file
*** Did not find GAMS name f_out in GDX file
*** Did not find GAMS name agg_out in GDX file
*** Did not find GAMS name par_comprdl in GDX file
*** Did not find GAMS name par_comprdm in GDX file
*** Did not find GAMS name par_comnetl in GDX file
*** Did not find GAMS name par_comnetm in GDX file
*** Did not find GAMS name par_eout in GDX file
*** Did not find GAMS name par_cumcst in GDX file
*** Did not find GAMS name eqg_combal in GDX file
*** Did not find GAMS name par_combalem in GDX file
*** Did not find GAMS name eqe_combal in GDX file
*** Did not find GAMS name par_combalgm in GDX file
*** Did not find GAMS name eq_peak in GDX file
*** Did not find GAMS name par_peakm in GDX file
*** Did not find GAMS name par_ipric in GDX file
*** Did not find GAMS name par_cumflol in GDX file
*** Did not find GAMS name par_cumflom in GDX file
*** Did not find GAMS name par_top in GDX file
*** Did not find GAMS name par_caplo in GDX file
*** Did not find GAMS name par_capup in GDX file
*** Did not find GAMS name Cap_New in GDX file
*** Did not find GAMS name cst_invc in GDX file
*** Did not find GAMS name cst_invx in GDX file
*** Did not find GAMS name cst_salv in GDX file
*** Did not find GAMS name cst_decc in GDX file
*** Did not find GAMS name cst_fixc in GDX file
*** Did not find GAMS name cst_fixx in GDX file
*** Did not find GAMS name cst_actc in GDX file
*** Did not find GAMS name cst_floc in GDX file
*** Did not find GAMS name cst_flox in GDX file
*** Did not find GAMS name cst_comc in GDX file
*** Did not find GAMS name cst_comx in GDX file
*** Did not find GAMS name cst_come in GDX file
*** Did not find GAMS name cst_irec in GDX file
*** Did not find GAMS name cst_pvp in GDX file
*** Did not find GAMS name cst_pvc in GDX file
*** Did not find GAMS name cst_time in GDX file
*** Did not find GAMS name val_flo in GDX file
*** Did not find GAMS name ObjZ in GDX file
*** Did not find GAMS name reg_wobj in GDX file
*** Did not find GAMS name reg_obj in GDX file
*** Did not find GAMS name reg_irec in GDX file
*** Did not find GAMS name reg_acost in GDX file
*** Did not find GAMS name par_ucsl in GDX file
*** Did not find GAMS name par_ucsm in GDX file
*** Did not find GAMS name par_ucmrk in GDX file
*** Did not find GAMS name par_ucrtp in GDX file
*** Did not find GAMS name par_ucmax in GDX file
--- VEDA Cube: DataRecords=0
*** Did not find GAMS text/set name "adesc" in GDX file
*** Did not find GAMS text/set name "sysuc" in GDX file
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\VEDA\VEDA_FE\GAMS_WRKTIMES>
Reply
#2
You have some GAMS compile time error (from base.dd), but the console output does not indicate what that error is.
Could you post the listing file from the run (*.lst, please zip-compress it), which will reveal the nature of the error.
Reply
#3
Here is the .lst in a compressed folder. is this the format that you requested?


Attached Files
.zip   EPAUS9rT_16_1_2ELCTax.zip (Size: 15.88 KB / Downloads: 9)
Reply
#4
Yes, thanks.

The fatal errors are related to duplicate entries in the set COM_DESC:
**** 8 Duplicate records for symbol COM_DESC

The problem thus appears to be in VEDA-FE. For some reason, with your model VEDA writes a few duplicate entries into that set.
It might help KanOrs to fix the problem if you can tell what changes you did into your model that caused these errors to start appearing? You might also be able to eliminate the errors by yourself if you know what started causing them.
Reply
#5
(25-02-2018, 01:06 AM)Antti-L Wrote: Yes, thanks.

The fatal errors are related to duplicate entries in the set COM_DESC:
**** 8 Duplicate records for symbol COM_DESC

The problem thus appears to be in VEDA-FE. For some reason, with your model VEDA writes a few duplicate entries into that set.
It might help KanOrs to fix the problem if you can tell what changes you did into your model that caused these errors to start appearing? You might also be able to eliminate the errors by yourself if you know what started causing them.

Thank you for your response. The only things I changed were the following: Start From Scratch, Do you want to select all components "YES", select only imported items "NO". I also added this scenario which is a tax of $100 per ton of ELCCO2 (the units are actually Million$ per Million tons). The excel file format for the added scenario seems to be an older version compared to the others for some reason, but not sure if that would cause this problem.


Attached Files
.xls   Scen_ELCCO2Tax.xls (Size: 39 KB / Downloads: 7)
Reply
#6
Ok, I don't think the scenario has anything to do with the error.

Did you then perhaps update your VEDA-FE just recently?  I think only KanOrs can help you with it further.

One thing for you to look at is the 1660 domain violation errors in your model, shown in the listing file. While these are only warnings, and you would still be able to run the model, they indicate modelling errors. They are all in base.dd.

For example, in some data parameters you have lots of labels like this:
PTCR~2020~2025~2030~2035~2040~20
They seem quite erroneous to me, and even if intended, they have not been defined in your model, and thus the domain violations.
Reply
#7
I suspect that most of your domain violations were due to using malformed ~COMEMI tables.

If you want to define time-variant emission coefficients à la COMEMI in a Base or Subres Template, see the figure below for an example (without creating erroneous commodity labels like PTCR~2020~2025~2030~2035~2040):

   

The table above defines emission factors (just like COMEMI) for some fuels for the years 2010, 2015 and 2020. For any other model years, the parameters are automatically inter-/extrapolated, and so the emissions remain constant for all years beyond 2015.
Reply
#8
Thank you very much for your reply and the table. I will try using the type of table!
Reply
#9
INDNGA is declared twice in file SysSettings Sheet Sec_Comm Rows 324/325
Reply
#10
Good detective work, Amit!

However, now I am puzzled about it, because when I try the same, by putting duplicate rows for some commodities in a ~FI_Comm table in SysSettings, I get no such error. Only one entry of COM_DESC for each pair (r,com) gets written into the DD file, which I find convenient.

What am I missing?  Does the problem appear only under some special circumstances? Or is it a (pseudo-) random issue?
Reply
#11
Try using different descriptions Smile
Reply
#12
I did try with both same and different descriptions. But no success in getting duplicate entries in the DD file Sad
What am I doing wrong?
Reply
#13
You are right Antti. VEDA handles duplicate commodity declaration, but not if the commodity with duplicate entries is declared for multiple regions (comma-separated entries in the Region column of ~FI_Comm table).

Let me know if you think it is important to include this case soon. Otherwise we will take care of this in the new version of VEDA.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)