25-04-2018, 01:40 PM
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...
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...
