Veda2.0 Released!


Appropriate solve parameter for large model
#16
Alright, thanks for the hints!
Yesterday, I did model runs all day long, comparing the run durations  (CPLEX time) between the former and your alternative suggestion for the milestone years, by letting the model run different ending years:

   
(One attempt up to the ending year 2050 is still underway on the workstation...)

The alternative milestone year definition seems to be better in some cases and worse in others, but since it seems to be a more straightforward definition, I will keep it for now.
I also checked and confirm that OBLONG is activated and tried explicitly the modified objective function definition, which did not show any difference.

Right now, I'm experimenting with different CPLEX parameters such as setting barepcomp to a somewhat higher value (1e-6, 1e-4, ...), but it also seems to have a rather small effect.

Yeah, so I would agree with you, it seems that I'm facing numerical problems. Therefore, another thing that came into my mind, would be rounding the AF and COM_FR values to, say, 5 or 6 digits behind the decimal point (right now they are not rounded at all and could, for example, be 0.170984708319).
Do you think that might mitigate numerical problems?

If nothings helps, I would enable a time-stepped solution or, as the ultimate last resort, decrease the temporal resolution of the model... Undecided
Reply
#17
Well, there are also some other things to check for improving numerical stability, for example:

• Remove dummy import processes from your model if you have such (e.g. NCAP_START(IMP*Z)=2200)
• Make sure you don't have any other artificially high costs in your model (to prevent some technology from entering the solution), and use zero bounds or NCAP_START instead

Even if the dummy imports are not active in the solution, they can cause poor numerical stability for the barrier algorithm if the processes are available in the model.
Reply
#18
Awesome, Antti! That was the major cause of the instability - I deactivated all dummy imports and the run times dropped tremendously both on the desktop and the workstation - have a look:    

Very big thank you for that!
Now I can even think of increasing the temporal resolution and/or adding more fancy future technologies... Big Grin
Reply
#19
Great, thanks for the very good news!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Model Import Yan Yan 8 2,442 30-01-2024, 05:45 PM
Last Post: Yan Yan
  NCAP_AFCS parameter not recognized Sandro_Luh 14 9,284 01-11-2021, 03:24 AM
Last Post: Antti-L
  Failure to reproduce a previous run from built model under Veda1.4 iris 1 2,180 19-05-2021, 09:23 PM
Last Post: Antti-L
  Multi-region parameter guozhi1305 2 3,324 03-05-2021, 04:19 PM
Last Post: guozhi1305
Photo SOLVE ISSUE JozefO 10 11,827 08-10-2020, 12:30 AM
Last Post: JozefO
  Problems to sync a small model with 8736 time-slices Pernille.S 21 37,575 28-05-2020, 12:01 AM
Last Post: AKanudia
  How can I model discharge times for two DAYNITE processes? ach 3 5,269 26-04-2020, 02:52 AM
Last Post: Antti-L
  Infeasibility in Model Runs Ismail Kimuli 0 2,111 24-02-2020, 10:49 AM
Last Post: Ismail Kimuli
  Model infeasible regardless of CO2 limit- not sure why? ach 2 5,006 10-12-2019, 04:39 AM
Last Post: Antti-L
  Solve Time Under SO2,NOX,PM2.5 Taxes mbr1818 4 8,166 23-03-2019, 10:24 PM
Last Post: Antti-L

Forum Jump:


Users browsing this thread: 1 Guest(s)