Veda2.0 Released!


Non-optimal results when 'fixed result to x period'
#1
I am trying to use Lodag GDX>'fixed years up to' attribute to run a scenario with a wide range of carbon budgets. I am fixing results to BAU scenario until 2020, so the model will optimize after this period. When I do this, I get 'solution available but not proven optimal due to numerical difficulties'. This happens even in scenarios which the carbon budgets are not that stringent, hence I would expect optimal results.
And the curious thing about (which made me post this here) is that if i fix results up to 2030, not up to 2020, then I reach optimal results. It does not make sense that I get optimal results when I fix results to BAU up to 2030 (hence a lower number of periods to invest on mitigation), but not when I fix results to BAU up to 2020.
Would anyone have a hint on what is happening and how to fix this?
 
Best,
Reply
#2
Well, if you fix results up to 2030, then you have a smaller model, which is thus easier to solve than when you fix up to 2020.  So, to me it does make sense that you then reach proven optimal results.  Blush

Anyway, the condition "solution available but not proven optimal due to numerical difficulties" means that the solver is running into some numerical difficulties while trying to complete the solution of the problem. When a model has such problems, the numerical difficulties typically may occur in a rather random manner: some model runs may complete well while others don't.

See this thread on the ETSAP Forum for several options that can be used for troubleshooting "Solution available but not proven optimal due to numerical difficulties":
https://iea-etsap.org/forum/showthread.php?tid=162

Nonetheless, getting rid of all dummy imports has in many cases proven to be the easiest and effective way of improving the numerical stability of large VEDA-TIMES models. Therefore, as the first thing to try I would suggest disabling the dummy imports (if you have enabled them):

* Disable dummy imports to improve numerical stability
  NCAP_START(R,'IMPNRGZ')=2200;
  NCAP_START(R,'IMPMATZ')=2200;
  NCAP_START(R,'IMPDEMZ')=2200;

Under VEDA, you can define these in any scenario file. Of course, disabling the dummy imports requires that your model is in fact feasible.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Results of UC_Growth are not matching with given constarint Anjali 12 10,222 02-09-2022, 02:03 PM
Last Post: anshfr
Photo Result Database Not Generated nadhilah.reyseliani81 9 12,070 28-02-2020, 07:20 PM
Last Post: Ravinder
  Terminated by solver/Optimal Lukas 2 5,283 27-01-2020, 01:56 PM
Last Post: Lukas
  Results DB Maker and .VD file JasonMcGuire 7 12,309 09-07-2019, 08:31 PM
Last Post: Antti-L
  Results in VEDA BE MohammedAbiAfthab 0 2,078 02-07-2019, 05:39 PM
Last Post: MohammedAbiAfthab
  importing results maria 6 13,832 14-06-2019, 09:44 PM
Last Post: Ravinder
  Demand projections and fixed initial years Pernille.S 1 3,415 29-05-2019, 09:28 PM
Last Post: Antti-L
  Could not open results in VEDA-BE Aymane 3 6,805 31-01-2019, 09:08 PM
Last Post: Aymane
  Terminated by solver with status being Optimal MikkelBosack 2 5,651 17-08-2018, 04:26 PM
Last Post: MikkelBosack
  Using inter-period storage to model waste treatment Xin Wang 7 14,613 12-01-2017, 08:24 PM
Last Post: Xin Wang

Forum Jump:


Users browsing this thread: 1 Guest(s)