Veda2.0 Released!


Unexpected Termination of Run!
#1
Hello everyone, my Veda always appears "Unexpected Termination of Run!" during operation.
Do any masters know why this appears? Attached is the LST file.
[font=Helvetica, "Microsoft Yahei", verdana]Regards,[/font]
[font=Helvetica, "Microsoft Yahei", verdana]Yunfei Han[/font]


Attached Files
.zip   BASE.zip (Size: 22.21 KB / Downloads: 6)
Reply
#2
The errors in the listing file suggest that you have a zero PRC_ACTFLO defined somewhere, which is a modeling error.  Can you post the  QA_Check.log file from this run?  It is written in the same folder as the listing file.

I also note that the listing file you provided is dated in November 2017, over five years ago. Have you set your computer date to 2017?
Reply
#3
(10-05-2023, 07:54 PM)Antti-L Wrote: The errors in the listing file suggest that you have a zero PRC_ACTFLO defined somewhere, which is a modeling error.  Can you post the  QA_Check.log file from this run?  It is written in the same folder as the listing file.

I also note that the listing file you provided is dated in November 2017, over five years ago. Have you set your computer date to 2017?

Thank you for your reply, but it seems that there is no QA_CHECK.log file here. As shown in the attached image.
Also, does the computer time need to be set to 2017? Does this have an impact on the model operation?


Attached Files Thumbnail(s)
   
Reply
#4
The listing file shows clearly that the file QA_CHECK.log has indeed been written:

**** REPORT FILE SUMMARY
QLOG C:\VEDA\Veda_FE\GAMS_WRKTIMES\QA_CHECK.LOG


However, the listing file also shows that when you have run the case, your computer time was November 8, 2017:

GAMS 24.7.1  r56632 Released Mar 14, 2016 WEX-WEI x86 64bit/MS Windows  11/08/17

I was asking you why this is so.  Please don't ask me why your computer time is such. But why is the time of your run 2017? I think it should be May 2023, but clearly it isn't.
Reply
#5
(11-05-2023, 12:41 PM)Antti-L Wrote: The listing file shows clearly that the file QA_CHECK.log has indeed been written:

**** REPORT FILE SUMMARY
QLOG C:\VEDA\Veda_FE\GAMS_WRKTIMES\QA_CHECK.LOG


However, the listing file also shows that when you have run the case, your computer time was November 8, 2017:

GAMS 24.7.1  r56632 Released Mar 14, 2016 WEX-WEI x86 64bit/MS Windows  11/08/17

I was asking you why this is so.  Please don't ask me why your computer time is such. But why is the time of your run 2017?  I think it should be May 2023, but clearly it isn't.

Sorry for that , I may have uploaded the wrong file. I have already uploaded a new LST file. Additionally, I have attached two diagrams of the GAMS program. I don't know what this means.


Attached Files Thumbnail(s)
       

.zip   BASE.zip (Size: 5.19 KB / Downloads: 6)
Reply
#6
Ok, thanks, the new listing file is better (looks like it is the right one).
However, the test model has severe problems, resulting in many compile time warnings and errors.

In particular, it seems that your region definitions are in some way quite messed up.
The following regions cause domain violations:

  gaoluliantie
  gaolupenchuiqingqiliantie
  lianjiao
  qiutuan
  REG1
  Region
  shaojie
  shaojie and qiutuan
  zhijiehuanyuan

I cannot help much about it without seeing the model, but perhaps the VEDA developers can help you further.
Anyway, for some reason, none of these regions seem to be defined as regions in your model, but they are still referred to in some attributes.  The regions "REG1" and "Region" also look suspicious as such, and the region "shaojie and qiutuan" causes a syntax error due to the spaces in the name.  I think VEDA-FE did have an option for enclosing labels in quotes to avoid that error; see Tools → User Options → General.
Reply
#7
(11-05-2023, 09:39 PM)Antti-L Wrote: Ok, thanks, the new listing file is better (looks like it is the right one).
However, the test model has severe problems, resulting in many compile time warnings and errors.

In particular, it seems that your region definitions are in some way quite messed up.
The following regions cause domain violations:

  gaoluliantie
  gaolupenchuiqingqiliantie
  lianjiao
  qiutuan
  REG1
  Region
  shaojie
  shaojie and qiutuan
  zhijiehuanyuan

I cannot help much about it without seeing the model, but perhaps the VEDA developers can help you further.
Anyway, for some reason, none of these regions seem to be defined as regions in your model, but they are still referred to in some attributes.  The regions "REG1" and "Region" also look suspicious as such, and the region "shaojie and qiutuan" causes a syntax error due to the spaces in the name.  I think VEDA-FE did have an option for enclosing labels in quotes to avoid that error; see Tools → User Options → General.

Thank you very much. Your answer was very helpful, and I will check it again.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Unexpected termination of run jonas.forsberg@ltu.se 8 9,620 29-03-2023, 01:56 PM
Last Post: Antti-L
  Unexpected Termination of run! guozhi1305 6 6,097 25-08-2020, 04:06 PM
Last Post: guozhi1305
  Unexpected termination of run finorgan 5 6,448 18-10-2019, 08:19 PM
Last Post: finorgan
  Unexpected termination of the VEDA-FE run seckg 3 5,185 21-09-2019, 07:25 PM
Last Post: Antti-L
  Unexpected Termination of Run when using Levelized Cost switch subhadipbhattacharya 5 6,988 28-06-2019, 06:44 PM
Last Post: Antti-L
  Unexpected Runtime termination subhadipbhattacharya 1 3,998 18-03-2019, 08:06 AM
Last Post: AKanudia
  Unexpected Termination of Run NeilGrant 4 7,474 26-02-2019, 09:41 PM
Last Post: AKanudia
  Levelised Cost Reporting Option - Unexpected termination of Run Giulia Realmonte 7 15,049 01-05-2018, 08:30 PM
Last Post: Antti-L
  Unexpected Termination of Run mbr1818 12 20,728 27-02-2018, 03:32 PM
Last Post: AKanudia
  unexpected termination of run Sharonchang 13 18,473 14-02-2018, 06:06 PM
Last Post: utsavjha

Forum Jump:


Users browsing this thread: 1 Guest(s)