Veda2.0 Released!


VEDA FE / GAMS Error
#1
Hello, 

While solving a 16 region model and this error (Input in data/compile; not finding GAMS name...) came up . Unfortunately I do not have the slightest inkling of what this error means and how to fix it. 

   

Any suggestions or recommendations would be greatly appreciated. 

Thanks. 

Kate
Reply
#2
You have some compilation errors.

It remains undisclosed what those errors are. Suggestions and recommendations to fix the errors would depend on the nature of the errors. Can you post the listing file (*.LST, ZIP/RAR compressed), which shows the errors?
Reply
#3
(20-06-2017, 03:54 PM)Antti-L Wrote: You have some compilation errors.

It remains undisclosed what those errors are. Suggestions and recommendations to fix the errors would depend on the nature of the errors.  Can you post the listing file (*.LST, ZIP/RAR compressed), which shows the errors?

Thank you for the response. I have posted the listing file in a ZIP file. The errors seem related to inconsistent dimensions for an element (what element, I do not know...). 


.zip   Reference_KXL200617.zip (Size: 74.16 KB / Downloads: 6)

Much appreciation! 

Kate
Reply
#4
Fine.  The crucial errors are the following:

1361399  CAN.2019.TU_OILCRDXL_CAN_USA_01.-.ANNUAL 0.94
****                                     $338   $170 $148
**** LINE   5005 BATINCLUDE  C:\VEDA\VEDA_FE\GAMS_WRKTIAM_KK\trade_parms_mid_kxl.dd
**** LINE     82 INPUT       C:\VEDA\VEDA_FE\GAMS_WRKTIAM_KK\Reference_KXL200617.RUN
1361400  USA.2019.TU_OILCRDXL_CAN_USA_01.-.ANNUAL 0.94
****                                     $338   $170 $161
**** LINE   5006 BATINCLUDE  C:\VEDA\VEDA_FE\GAMS_WRKTIAM_KK\trade_parms_mid_kxl.dd
**** LINE     82 INPUT       C:\VEDA\VEDA_FE\GAMS_WRKTIAM_KK\Reference_KXL200617.RUN

As you can see, the dimension arguments given for these parameters are incomplete, as there is "-" in the second to last argument position. So, your input data specification in the scenario trade_parms_mid_kxl is erroneous for these parameter instances. Just fix those parameters there, and the fatal errors should be gone.

Note that I am not fully sure which TIMES attribute this is; but you would be able to see it by looking at the file trade_parms_mid_kxl.dd, lines 5005 and 5006.
Reply
#5
Antti-L, thank you so very much for your help! The error has been resolved.

Many thanks,

Kate
Reply
#6
Great!
For curiosity, can you still tell me, which TIMES attribute was in question, the erroneous one defined for TU_OILCRDXL_CAN_USA_01?
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Persistent Import Error after Sync Ismail Kimuli 0 193 02-03-2024, 02:54 PM
Last Post: Ismail Kimuli
  Veda Help Saad Awan 2 631 11-07-2023, 02:51 PM
Last Post: Saad Awan
  Veda Help Saad Awan 15 2,853 11-07-2023, 12:55 PM
Last Post: AKanudia
  Veda Errors Saad Awan 0 346 03-07-2023, 06:10 PM
Last Post: Saad Awan
  Veda Errors Saad Awan 2 752 16-06-2023, 04:06 PM
Last Post: Saad Awan
  VB error Samaneh 10 12,513 29-09-2022, 03:05 PM
Last Post: Ravinder
  ODBC Driver error while synchronizing juan.correalaguna@vito.be 1 1,188 31-03-2022, 06:13 PM
Last Post: Ravinder
  CPLEX Error 1707 - Infeasibility, but can't find where henriqueanjos 3 2,698 30-07-2021, 11:41 PM
Last Post: Antti-L
  "automation error interface" error shivika 4 3,942 17-06-2021, 07:32 PM
Last Post: Ravinder
  "automation error interface" error shivika 0 1,181 17-06-2021, 02:13 AM
Last Post: shivika

Forum Jump:


Users browsing this thread: 1 Guest(s)