Closed giannisvrochidis closed 6 months ago
UPDATE: The retire_min_period option worked. The retire_forced is not working (missing also from the excel input file) and from a quick search in the flexmodel3.mod it does not seem to be referenced anywhere. So I suppose, it's not yet implemented?
Thanks Giannis. You seem to completely right. The implementation in FlexModel3.mod is missing. Fully same functionality can be achieved using retire_min_period and retire_max_period set to the same value. We decided to drop the retire_forced from the input data - reducing number of available parameters is a plus (while not having a single parameter for this purpose is a minus).
To be implemented.
Thanks for the answer! On a related matter, is something like invest_forced implemented or same as with retire_forced?
It has the same thing - it's in the init.sqlite db, but not actually used.
Hello,
I have been trying to deploy the retire_forced parameter in an invest model,but the forced retirement is not taking place. I have tried using the retire_period, invest_retire_period and invest_retire_period_total investment methods, but in all cases the capacity of the unit I am trying to forcefully retire stays intact.
Additionally, I tried also using the retire_min_period and the following occured: 1) when combined with retire_period, no effect at all, capacity stays intact. 2) when combined with invest_retire_period and invest_retire_period_total or retire_period_total, the model throws an infeasibility (I Tried also adding a quite relaxed retire_max_period parameter to make sure it's not been caused by the relation between min and max).
Could it be FlexTool-related or setup-related?
Thanks in advance for your answers. Giannis