ERRORS IN INPUT DATA/COMPILE

[JozefO]

Hello, i reinstall GAMS to lower version because license expiration.

But after SOLVE ther is no RESULT. 

I m posting here LST. file from Gams Wrk folder. 
Old Veda worked fine with my test model. 

______________________________________________________________________________________
GAMS 24.8.5  r61358 Released May 10, 2017 WEX-WEI x86 64bit/MS Windows                                                                                                                                                                 12/18/20 12:16:29 Page 8
TIMES -- VERSION 4.1.0
C o m p i l a t i o n


 452  OPTION PROFILE=1, SOLVEOPT=REPLACE;
 453  OPTION RESLIM=50000, ITERLIM=999999, LIMROW=0, LIMCOL=0, SOLPRINT=OFF;
 454   
 455   
 456  option LP=CPLEX;
 457   
 458   
 459  *--If you want to use an optimizer other than cplex/xpress, enter it here:
 460  *OPTION LP=MyOptimizer;
 461   
 505  /
****  $460
**** LINE      3 BATINCLUDE  C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM_ts.dd
**** LINE     52 INPUT       C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM.RUN
GAMS 24.8.5  r61358 Released May 10, 2017 WEX-WEI x86 64bit/MS Windows                                                                                                                                                                 12/18/20 12:16:29 Page 9
TIMES -- VERSION 4.5.0
C o m p i l a t i o n


      *===========================================================================================
      *  Copyright © 2000-2020 IEA Energy Technology Systems Analysis Programme (IEA-ETSAP).
      *  This software (ETSAP TIMES) is open source: you can redistribute it and/or modify it
      *  under the terms of the GNU General Public License v3.0 (see file LICENSE.txt).
      *  For further information, visit: .
      *
      *  This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
      *  without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
      *===========================================================================================
GAMS 24.8.5  r61358 Released May 10, 2017 WEX-WEI x86 64bit/MS Windows                                                                                                                                                                12/18/20 12:16:29 Page 10
TIMES -- VERSION 4.5.0 -- Restart (v4.4)
C o m p i l a t i o n


2851  $ABORT  "*** ERRORS IN INPUT DATA/COMPILE ***"
****       $343
**** LINE     45 BATINCLUDE  C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\err_stat.mod
                             %3  *** ERRORS IN INPUT DATA/COMPILE ***
                             %2  ABORT
                             %1  $IF NOT ERRORFREE
**** LINE     46 BATINCLUDE  C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\maindrv.mod
                             %1  mod
**** LINE     75 INPUT       C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM.RUN
GAMS 24.8.5  r61358 Released May 10, 2017 WEX-WEI x86 64bit/MS Windows                                                                                                                                                                12/18/20 12:16:29 Page 11
TIMES -- VERSION 4.5.0 -- Restart (v4.4)
Error Messages


343  Abort triggered by above statement
460  Empty data statements not allowed. You may want to use $ON/OFFEMPTY

**** 2 ERROR(S)   0 WARNING(S)
GAMS 24.8.5  r61358 Released May 10, 2017 WEX-WEI x86 64bit/MS Windows                                                                                                                                                                12/18/20 12:16:29 Page 12
TIMES -- VERSION 4.5.0 -- Restart (v4.4)
Include File Summary


   SEQ   GLOBAL TYPE      PARENT   LOCAL  FILENAME

     1        1 INPUT          0       0  C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM.RUN
     2      502 BATINCLUDE     1      52  .C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM_ts.dd
     3      510 BATINCLUDE     1      56  .C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initsys.mod
     4      691 BATINCLUDE     3     181  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\units.def
     5      712 BATINCLUDE     3     184  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\maplists.def
     6      836 BATINCLUDE     3     187  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\globals.def
     7      855 BATINCLUDE     1      59  .C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initmty.mod
     8     1514 IF EXIST       7     672  .C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\gamssave\nul
     9     1576 BATINCLUDE     7     734  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\main_ext.mod
    10     1596 IF EXIST       9      20  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initmty.DSC
    11     1596 BATINCLUDE     9      20  ...C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initmty.DSC
    12     1620 IF EXIST       9      20  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initmty.VDA
    13     1620 BATINCLUDE     9      20  ...C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\initmty.VDA
    14     1703 IF EXIST       7     750  .C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM~data.gdx
    15     1707 BATINCLUDE     1      63  .C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\base.dd
    16     2643 BATINCLUDE     1      64  .C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\syssettings.dd
    17     2678 BATINCLUDE     1      75  .C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\maindrv.mod
    18     2701 BATINCLUDE    17      23  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\setglobs.gms
    19     2780 GDXOUT        18      46  ..C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\_dd_.gdx
    20     2806 BATINCLUDE    17      46  ..C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\err_stat.mod


COMPILATION TIME     =        0.046 SECONDS      3 MB  24.8.5 r61358 WEX-WEI


USER: Medium MUD - 10 User License                   S170221:0332CO-WIN
      Ministry of Environment, Institute for Environmental PolicDC13109


**** FILE SUMMARY

Restart    C:\TIMES-VEDA2.0\Veda\GAMS_SrcTIMES.v4.5.0\_times.g00
Input      C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM.RUN
Output     C:\TIMES-VEDA2.0\Veda\GAMS_WrkTIMES\WEM\WEM.lst

**** USER ERROR(S) ENCOUNTERED

[Antti-L]

Your SET ALL_TS is empty (see WEM_ts.dd).  This appears to be a VEDA glitch.
Until very recently, GAMS does not allow empty data statements, unless $ONEMPTY is used.

But do you really not have any timeslices in the model? If that is indeed the case, I guess the workaround in VEDA is to define ANNUAL as a SEASON timeslice (although it should actually never be defined such).

[JozefO]

Your SET ALL_TS is empty (see WEM_ts.dd).  This appears to be a VEDA glitch.
Until very recently, GAMS does not allow empty data statements, unless $ONEMPTY is used.

But do you really not have any timeslices in the model? If that is indeed the case, I guess the workaround in VEDA is to define ANNUAL as a SEASON timeslice (although it should actually never be defined such).

Im not sure what is the meaning of empty SET ALL_TS. Can you be more specific  please ?

I have an Annual timeslice defined in SysSettings.
Need to see my model ?

~TimeSlices
Annual
ANNUAL

[Antti-L]

I have an Annual timeslice defined in SysSettings.

~TimeSlices
Annual
ANNUAL

In essence, that is just perfect. But as I said, there appears to be a VEDA glitch causing that ANNUAL to be ignored. See the file WEM_ts.dd to verify. As I said already, I guess the workaround in VEDA is to define ANNUAL as a SEASON timeslice (although it should actually never be defined such). My sincere apologies for the inconvenience.

[JozefO]

I have an Annual timeslice defined in SysSettings.

~TimeSlices
Annual
ANNUAL

In essence, that is just perfect. But as I said, there appears to be a VEDA glitch causing that ANNUAL to be ignored. See the file WEM_ts.dd to verify. As I said already, I guess the workaround in VEDA is to define ANNUAL as a SEASON timeslice (although it should actually never be defined such). My sincere apologies for the inconvenience.

 OK do not worry i fixed it. It should be working now. Thank you Antti very much.

[JozefO]

I have an Annual timeslice defined in SysSettings.

~TimeSlices
Annual
ANNUAL

In essence, that is just perfect. But as I said, there appears to be a VEDA glitch causing that ANNUAL to be ignored. See the file WEM_ts.dd to verify. As I said already, I guess the workaround in VEDA is to define ANNUAL as a SEASON timeslice (although it should actually never be defined such). My sincere apologies for the inconvenience.

Finally i got result but  but  after Sync Resul  i got pop up windows "Selected files do not contain any TAGs which can be read with veda.

[AKanudia]

Can you post the model here?

[JozefO]

Can you post the model here?

Hi Amit yes here it is.

And i have noticed that there are some differencies between old and new VEDA.

In SysSetting (new VEDA) is missing sheet Import Settings with some options like a Create dummy import for Energy an Material Commodities and so on. 
Demo Models has new Excel file named Sets-DemoModels. It is necessary to have it instead "Import Settings" in SysSettings file ? 

And i got a totally different results in new VEDA compared to old VEDA. 

Every process has dummy import.  It is little bit consusing.

[AKanudia]

Veda2.0 forces you to control the costs of dummy imports in SysSettings (or some other scenario). just declare some high costs for pset_pn=IMP*Z and things should improve.

[JozefO]

Veda2.0 forces you to control the costs of dummy imports in SysSettings (or some other scenario). just declare some high costs for pset_pn=IMP*Z and things should improve.

Hi Amit i have manually created Sets-file because Veda_SnT to Excel migration does not work in my case. It only create an empty excel file. What if is model building up from scratch in VEDA 2.0 how is Sets file created then ? 

... i m posting here my file "Sets", could you look at dummy imports issue ?

Best regards

[AKanudia]

Post the SnT MDB and I will migrate it.

dummy imports cost is an unrelated issue. just declare ACT_COST of IMP*Z as 9999 or something via an INS table in SysSettings

[JozefO]

Post the SnT MDB and I will migrate it.

dummy imports cost is an unrelated issue. just declare ACT_COST of IMP*Z as 9999 or something via an INS table in SysSettings

Ok i have set ACT_COST of IMP*Z as 9999 in SysSett. but still (my demand commodities and processes are as dummy import). I m confused, old veda did not do that. 

Here is my SnT file .

[AKanudia]

This file does not contain any set definitions. If you have created sets, you need to post the SnT file from the model database folder.

[AKanudia]

here is your modified model where I have only declared costs for dummy imp, and I don't see them in the solution anymore.