ifference between revisions of "EMK:Run Window"
Line 47: | Line 47: | ||
==Schedules Box== | ==Schedules Box== | ||
+ | '''''Schedules''''' allow you to control various aspects of the model at run time. Using a '''''[[EMK:Schedules | Schedule Resource]]''''' in a Run is optional, but any Schedules used must be listed in the '''Schedules Box.''' | ||
+ | |||
+ | '''Schedules Box Fields''' | ||
+ | {|class="wikitable" | ||
+ | |- | ||
+ | | ''Name'' || Specifies which Schedule Resource is to be used | ||
+ | |- | ||
+ | | ''Description'' || A free text field for supplementary information about the Schedule Resource | ||
+ | |} | ||
+ | |||
+ | Note: Multiple Schedule Resource Instances can be used in a Run Definition. Where the same constant, variable or function is used in different Schedules associated with a Run, EMarket will use the last definition to be read for that constant, variable or function - no warning will be given that this has taken place. | ||
==Volatility Matrix== | ==Volatility Matrix== | ||
[[EMK:Forecasting | Back to Forecasting]] | [[EMK:Forecasting | Back to Forecasting]] |
Revision as of 16:31, 14 November 2012
Run Parameters Box
This is located at the top left and contains general Run Parameters.
Run Parameters Box Fields
Connections | Specifies the Connections Resource to be used |
Start Date | The Run will begin at 00:00am on this date. |
Demand Regions | specifies which Demand set ( Regions Resource) is to be used |
Dispatch Mode | One of three pre-defined settings determining the method used to solve the dispatch problem:
|
Reserve Config | Specifies which Reserve Resource is to be used - however this is only effective when Nodal+Reserves is selected in the Dispatch Mode field. |
Company Opt | When set to True any company in the Connections Resource set to Optimise Offers will have company optimisation implemented. . That is, the Company's exposure to Prices from retail load, to hedges, and market power are used to adjust the Company's Offers in order to optimise gross profit. If this option is set to False, then no company optimisation adjustments will be made. |
Binary Outputs | Specifies which Binary Output set is used. |
Reports Batch | Specifies the Reports Batch Resource which defines the Reports automatically produced with the Run. If no Reports Batch is attached, then no Reports will be produced automatically at the end of the Run. But note that Reports can be updated and produced at any time, via the Reports Resource. |
Random Outage Seed | Determines the pattern of random Generator outages for a Run.
As well the three pre-defined fields, variables from the Volatility Matrix are also available as seeds. These variables appear along with the pre-defined seeds in the field's selection list (the Inflow year option will be a frequently used example). |
Demand Box
The Demand Box is used to set the annual Demand (in GWh) associated with each Region in the Regions Resource specified in the Run Definition.
Demand Box Fields
Region | each Region field lists a Region that has been setup in the Regions Resource. The Region names cannot be edited from this box |
Demand (GWh) | Specifies the Demand figure in GWh against each Demand Region. |
Schedules Box
Schedules allow you to control various aspects of the model at run time. Using a Schedule Resource in a Run is optional, but any Schedules used must be listed in the Schedules Box.
Schedules Box Fields
Name | Specifies which Schedule Resource is to be used |
Description | A free text field for supplementary information about the Schedule Resource |
Note: Multiple Schedule Resource Instances can be used in a Run Definition. Where the same constant, variable or function is used in different Schedules associated with a Run, EMarket will use the last definition to be read for that constant, variable or function - no warning will be given that this has taken place.