That’s basically true. To be more specific, RAMP_10 is used to determine the 
amount that a contingency dispatch can deviate from the corresponding base 
case, or to limit the reserve supplied by a unit when using fixed zonal reserve 
requirements. And RAMP_30 is used to determine how much a base case dispatch in 
a particular period can deviate from the base case dispatches in adjacent 
periods. And RAMP_AGC is not currently used for anything.

In MOST there are essentially two types of “reserve”: (1) contingency reserve, 
and (2) load-following ramp reserve. The contingency reserve, limited by 
RAMP_10, can be handled in one of two ways, either by specifying fixed zonal 
reserve requirements (in a deterministic problem) or by specifying explicit 
contingencies that must be covered (in a stochastic problem). This is discussed 
in Section 3.2 of the MOST User’s Manual 
<> and defined by 
equations (4.16)–(4.22). The load-following ramp reserve, limited by RAMP_30, 
is described in Section 3.5 and defined by equations (4.23)–(4.27).

Hope this helps,


> On Mar 8, 2018, at 7:29 PM, Stephen Suffian <> wrote:
> I believe I've seen a similar question asked before. See this link 
> <> which 
> indicates that RAMP_10 is used for reserve calculations, RAMP_30 for dispatch 
> scheduling, and RAMP_AGC Is not currently used by matpower according to this 
> link <>.
> On Thu, Mar 8, 2018 at 6:51 PM, Bainan Xia < 
> <>> wrote:
> Hi,
> I’m running a huge power system simulation using MOST recently. I’ve got some 
> information on ‘ramp rate (% of the rated capacity per min)’ for each type of 
> generator from a paper. I would like to add these constraints into my case. 
> I’ve found a field in mpc.gen, called ‘RAMP_AGC’, which is ramp rate for load 
> following/AGC (MW/min). I’m wondering whether that is the right place to 
> fill. Or the following columns ‘RAMP_10’ and ‘RAMP_30’ are the right choices. 
> I’m also a little confused on the difference between ‘RAMP_10’ and ‘RAMP_30’. 
> What does the word ‘reserve’ mean in the documentation.
> Thanks for the help J
> Best,
> Bainan

Reply via email to