Dear all,
I am attempting to use MOST to formulate a DC security constrained OPF, with preventive and corrective redispatch/curtailment. If I understand MOST's approach to security correctly, it is aimed at determining a base case dispatch (e.g. a day-ahead schedule), and corresponding contingency state dispatches (e.g. a real-time dispatch) that are reachable from the base case (within ramping and reserve constraints). Hence, the approach is mostly corrective, yet some preventive action is also taken as the optimization attempts to converge to a secure base case dispatch. By assigning the PositiveActiveDeltaPrice and NegativeActiveDeltaPrice, it is possible to set a preference for the generators to use for corrective actions, by penalizing them more or less compared to the others. Now, in my case the grid is being supplied by a number of wind generators that can be curtailed to any value below PMAX. When I remove all corrective costs, and set the maximum contingency reserves to 0, the dispatch in base case and all contingency states will be "preventively" secure (and equal). However, the dispatch is made entirely on a market basis (all curtailments are driven by the generator cost functions). I would therefore like to add penalty costs, say, a curtailment cost per MW that the base case deviates from PMAX. That way, for preventive actions it is possible to control which generators are most likely to curtail. Is there a straightforward/documented way to edit the objective function and achieve this? I have seen a similar question previously (https://www.mail-archive.com/[email protected]/msg07231.html) where the response was to add new variables / constraints in the appropriate places of the most.m file, but I struggle to find documentation on how this works exactly. Kind regards, Igor Verbruggen
