Difference between revisions of "EMK:Run Parameters Box"
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{#hidens:}} | {{#hidens:}} | ||
+ | The '''Run Parameters Box''' identifies the run definition and specifies the Input Resource Instances to be used at run time. | ||
+ | |||
+ | ;'''Run Parameters Box Fields''' | ||
+ | |||
+ | ---- | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | Name || The display name of the Run Definition Instance | ||
+ | ---- | ||
+ | Note: Developing your own standardized naming convention is recommended | ||
+ | |- | ||
+ | | Description || A descriptive text field for additional run information | ||
+ | |- | ||
+ | | Connections || Specifies the ''''Connections Resource'''' to be used at run time, i.e. the configuration of the Grid and it's connected Generators | ||
+ | |- | ||
+ | | Start Date || The date from which the Run Definition will Forecast from. The Run always begins at 00:00am on the Start Date entered in this field even when a later time is entered | ||
+ | |||
+ | Example: 30 July 2003 02:30:00. The Run will start at midnight on 30 July 2003. | ||
+ | |- | ||
+ | | 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: | ||
+ | *''Nodal'': nodal pricing with energy dispatch only (the most commonly used dispatch mode) | ||
+ | *''Nodal+Reserves'': energy and Reserves dispatch co-optimisation. | ||
+ | *''Simple'': simple merit order dispatch method in which transmission losses and limits are ignored, i.e. Offer Bands are dispatched solely on the basis of their price, in the order of lowest to highest. In simple mode all 'nodal' prices throughout the country will be the same for any particular Tick. | ||
+ | |- | ||
+ | | Reserve Config || Specifies which Reserve set (''''Reserve Resource'''') is to be used - this is only effective when "Nodal+Reserves" is selected in the ''Dispatch Mode'' field. | ||
+ | |- | ||
+ | | Company Opt || When ''Company optimisation'' is set to 'True' any Company in the '''Connections Resource Instance''' 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 ''''(Binary Output Resource)'''' is used at run time. The default setting is "Default" which has a typical selection but does not include all possible output data. | ||
+ | ---- | ||
+ | Note: It is likely that the Binary Output requirements will vary from Run to Run. Optimal Binary Output selection will provide the data needed for Reporting purposes without overloading hard disk capacity. While it is possible to always output all binary data, be aware that this will use up disk space and slow down the execution of runs. | ||
+ | |- | ||
+ | | 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.<br/>There are three pre-defined settings for the random outage seed value which appear in the field's selection list: | ||
+ | *''Version:'' tells the Run to use every combination of variables defined in the '''Volatility Matrix''' box as an outage seed. For example, if the variable Inflow Year has values 1931-1932, and variable V2 has value 1, then there will be the generation outage pattern will be consistent from Run to Run with the setting 'Version' if no other changes have been made to the Run setup. This is the setting you will probably use the most. | ||
+ | *''Rand:'' causes the outage pattern to be random for any Generator with an ''Availability'' less than one. | ||
+ | *''Constant:'' forces a particular outage pattern to occur for a Run every time it is submitted regardless of changes to any setting for that Run. However, it is unlikely that Runs created with different input data will have the same outage pattern with this setting. | ||
+ | |||
+ | 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). | ||
+ | ---- | ||
+ | Note: The percentage of time that a Generator is available for generation is set as a percentage in the Availability field of a Generator's ''''Generator Editor.'''' ''EMarket'' allocates the remaining, non-available time as random outages. The use of the Availability setting is discussed in the ''''The Generator Resource section.'''' | ||
+ | |} | ||
[[EMK:The Run Definition Editor | Back to The Run Definition Editor]] | [[EMK:The Run Definition Editor | Back to The Run Definition Editor]] |
Latest revision as of 08:26, 8 November 2012
The Run Parameters Box identifies the run definition and specifies the Input Resource Instances to be used at run time.
- Run Parameters Box Fields
Name | The display name of the Run Definition Instance
Note: Developing your own standardized naming convention is recommended |
Description | A descriptive text field for additional run information |
Connections | Specifies the 'Connections Resource' to be used at run time, i.e. the configuration of the Grid and it's connected Generators |
Start Date | The date from which the Run Definition will Forecast from. The Run always begins at 00:00am on the Start Date entered in this field even when a later time is entered
Example: 30 July 2003 02:30:00. The Run will start at midnight on 30 July 2003. |
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 set ('Reserve Resource') is to be used - this is only effective when "Nodal+Reserves" is selected in the Dispatch Mode field. |
Company Opt | When Company optimisation is set to 'True' any Company in the Connections Resource Instance 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 '(Binary Output Resource)' is used at run time. The default setting is "Default" which has a typical selection but does not include all possible output data.
Note: It is likely that the Binary Output requirements will vary from Run to Run. Optimal Binary Output selection will provide the data needed for Reporting purposes without overloading hard disk capacity. While it is possible to always output all binary data, be aware that this will use up disk space and slow down the execution of runs. |
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. There are three pre-defined settings for the random outage seed value which appear in the field's selection list:
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). Note: The percentage of time that a Generator is available for generation is set as a percentage in the Availability field of a Generator's 'Generator Editor.' EMarket allocates the remaining, non-available time as random outages. The use of the Availability setting is discussed in the 'The Generator Resource section.' |