The RAMP_10 and RAMP_30 columns of the gen matrix are used to define the 
physical ramping capability of the generator. RAMP_10 limits the difference 
between base and contingency dispatches (or the amount of reserves a unit can 
supply when using a fixed zonal reserve requirement). RAMP_30 limits the 
ramping between periods in the unit commitment or multiperiod dispatch problem.

The values of PositiveLoadFollowReserveQuantity and 
NegativeActiveReserveQuantity can be used to further restrict the ramping of 
the unit, if desired, to something smaller than its physical capabilities.In 
the example in 7.2.2 setting it to 250 does not actually “remove” the 
constraint, it simply makes it large enough that it is no longer binding. I 
suppose it would have been more obvious if I’d set it to something greater than 
or equal to the full capacity of the unit, like 600 MW or something.

Hope this helps,

     Ray


> On Sep 10, 2016, at 10:58 AM, Tatiana Carolina Cantillo Garcia 
> <tcanti...@uninorte.edu.co> wrote:
> 
> Dear all, 
> I am a little confused about setting ramp constrains in MOST.  If I have 
> understood right one must set the  'PositiveLoadFollowReserveQuantity’ and 
> the 'NegativeActiveReserveQuantity' of the xgd matrix to the desired ramp 
> constrains. But I don’t really get how to remove ramp constrains; I was 
> checking the Deterministic Unit commitment example in section 7.2.2 in the 
> MOST manual and I don’t really get why when the 
> PositiveLoadFollowReserveQuantity of Generator 3 is set  to 250 the ramp 
> constrain is removed. Could someone explain it to me?  
> On the other side, could anyone explain me what values one must set in the  
> RAMP_10 and RAMP_30 columns of the mpc.gen matrix? And are in some way those 
> values used in the Unit commitment problem formulation in MOST?
> 
> Thank you very much in advance,  
> Tatiana Cantillo
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Este correo no representa opinión o consentimiento oficial de la Universidad 
> del Norte, por lo que esta no adquiere ninguna responsabilidad por su 
> contenido, salvo en el caso de funcionarios en ejercicio de atribuciones 
> reglamentarias. Puede provenir de una cuenta ofrecida a funcionarios o 
> estudiantes, como parte del ejercicio educativo, evento en el cual tanto el 
> mensaje como sus anexos son estrictamente confidenciales. Ha sido analizado 
> con software antivirus; no obstante, no se garantiza que sea seguro o no 
> contenga errores o virus, por lo que la Universidad del Norte no se hace 
> responsable de su transmisión.

Reply via email to