Actually, at t=0 you only have InitialPg (not Pmin/Pmax), so the issue is really about setting Pmin/Pmax to a different value for t=1 than for all subsequent periods. By default, the generator limits defined in the mpc.gen matrix will be used for all periods. In general, any parameter that changes from period to period is handled using profiles. This is usually fine, but in this case, where you just want to specify a different value for t=1, it’s a bit cumbersome. In addition to Section 5.1.6 on profiles in the Manual, I suggest looking at one of the examples that uses a wind profile (which essentially modifies Pmax) to see how it’s done.
Hope that helps, Ray > On Mar 8, 2017, at 10:20 AM, Stephen Suffian <[email protected]> wrote: > > Dear all, > > I have a follow-up question to a previous email > <http://www.mail-archive.com/[email protected]/msg05428.html> (message > 05428). Someone asked about ramp constraints being violated on multi-period > unit commitment runs between t=0 and t=1, and the response was > > "Accordingly, MOST does not actually put constraints on the ramping > transitions from t=0 to t=1; if this is really needed, then you need to > modify the Pmax and Pmin of the generators at t=1 based on the ramping limit > and the value of the InitialPg parameter. This might need some revising of > the manual." > > I was wondering if someone could provide guidance on how to change the values > of Pmin and Pmax so that they are different between t=0 and t=1. In the > mpc.gen array, it appears that Pmax and Pmin allow only scalar values for > each generator. > > Thanks! > > Stephen Suffian
