Assuming I understand the situation correctly, it sounds like a situation where the value of the commitment status variable has no impact on the overall objective function. That is “on” and dispatched at zero vs. “off” results in exactly the same total objective function value. If so, there is no reason to expect the optimization algorithm to set the commitment to be “off”.
I suppose it might be nice to add some post-processing code MOST to check any units that are “on” and dispatched at zero and manually set their commitment to “off” if that solution is feasible and cost is not affected. Anyone want to take a crack at adding that? Ray On May 5, 2020, at 8:07 PM, Carlos E Murillo-Sanchez <ce.murillosanc...@gmail.com<mailto:ce.murillosanc...@gmail.com>> wrote: Carlos Ferrandon Cervantes wrote: Hello everyone: I’ve been working quite a while with a UC problem in MOST, using the IEEE RTS. I realised that when I compare the mdo.UC.CommitSched results with mdo.results.ExpectedDispatch there are differences in the commitment status and real power output. This happens only with machines with zero starting cost in my system. i.e. hydro and wind. Say for example, I have a commitment status of 1, but a power output of 0 for certain machine. In some cases, i have six hydro units In a bus, and there could be differences in three of them. It might be a dumb question, but do you have an idea why this could be happening ? or how should I interpret this results? Thank you so much in advance and stay safe, Carlos -- Carlos Ferrandon Carlos: I've had this happen if, for example, I forget to add some kind of sensible RAMP_30 number for a unit. A zero there might produce this behavior. Carlos.
