EMK:Functional Architecture - Revision history

Sisep: /* The Run Definition */

2013-02-07T20:19:07Z

The Run Definition

Sisep: /* The Run */

2013-02-07T20:14:14Z

The Run

Sisep: /* The Run */

2013-02-07T20:12:21Z

The Run

Sisep: /* The Run */

2012-12-04T02:46:11Z

The Run

Sisep at 20:57, 19 November 2012

2012-11-19T20:57:38Z

Sisep: /* The Run Definition */

2012-11-19T20:56:57Z

The Run Definition

Sisep at 20:40, 19 November 2012

2012-11-19T20:40:16Z

Sisep: /* The Run */

2012-11-19T20:39:32Z

The Run

Sisep: /* The Run */

2012-11-19T20:36:20Z

The Run

Sisep: /* The Run */

2012-11-19T20:15:41Z

The Run

@@ Line 75: / Line 75: @@
 The Run Definition Resource determines how EMarket will execute a Run.
-More information on how this is created can be found in the [[EMK:Run Window | Run Window]] section.
+More information on how this is created can be found in the '''''[[EMK:Run Window | Run Window]]''''' section.
 Multiple Runs can be executed from a single Run Definition over time. However, a Run Definition can also be changed at any time even when Forecast data has already been produced using the Definition.  In other words several differing sets of Results data can be made using the same Run Definition.  To ensure that Results can always be interpreted against the exact Run Definition Instance used to produce them, each Run completed in EMarket is assigned a unique Batch number.  The Batch number is used to name a sub-folder containing the Run Results data together with a copy of the Run Definition Instance used by the Run.  This allows the context of a set of Results to be recreated at a future time (conditional upon certain input data such as Demand profiles being subject to appropriate version control and backup). The numbered sub-folder is located in the Results data folder in the current Working Directory, under the name of the relevant Run Definition.

@@ Line 41: / Line 41: @@
 '''Iterative Dispatch'''
-Once equipped with a set of Water Values and a valid Definition the Run progresses to solving a series of dispatch cases. Each case requires a single execution of the dispatch engine (and may include execution of the short term river chain optimisation, volatility and Company optimisation engines). A single case represents a basic unitary time period, called a Tick, which can range in duration from one half hour to one week. In most instances Forecast data produced by the Run will contain one value per [[EMK:Entity.Traits | Entity.Trait]] per Tick. The Tick duration and number of ticks (Forecast duration) for a Forecast are determined in the [[EMK:Run Window | Run Window]].
+Once equipped with a set of Water Values and a valid Definition the Run progresses to solving a series of dispatch cases. Each case requires a single execution of the dispatch engine (and may include execution of the short term river chain optimisation, volatility and Company optimisation engines). A single case represents a basic unitary time period, called a Tick, which can range in duration from one half hour to one week. In most instances Forecast data produced by the Run will contain one value per [[EMK:Entity.Traits | Entity.Trait]] per Tick. The Tick duration and number of ticks (Forecast duration) for a Forecast are determined in the '''''[[EMK:Run Window | Run Window]].'''''
 It is possible to have multiple Tick types in a single Run Definition. Forecast data produced from such a Definition will contain outputs at different levels of granularity (e.g. some half hourly and some four hourly data). However where a Run involves mixed Tick types the output data will be continuous from start to end over the whole Forecast (i.e. no gaps) and also contiguous (i.e. no overlaps).

@@ Line 37: / Line 37: @@
 Typically Water Values are calculated in a single preliminary step at the start of a Run. However, it is possible pre-calculate Water Values as an independent operation, and to instruct EMarket to use these Water Values at run time.
-For more information on Water Values see: [[EMK:Water Values | Water Values]]
+For more information on Water Values see: '''''[[EMK:Water Values | Water Values]]'''''
 '''Iterative Dispatch'''

← Older revision		Revision as of 02:46, 4 December 2012
Line 36:		Line 36:

	Typically Water Values are calculated in a single preliminary step at the start of a Run. However, it is possible pre-calculate Water Values as an independent operation, and to instruct EMarket to use these Water Values at run time.		Typically Water Values are calculated in a single preliminary step at the start of a Run. However, it is possible pre-calculate Water Values as an independent operation, and to instruct EMarket to use these Water Values at run time.
		+
		+	For more information on Water Values see: [[EMK:Water Values \| Water Values]]

	'''Iterative Dispatch'''		'''Iterative Dispatch'''

← Older revision		Revision as of 20:57, 19 November 2012
Line 80:		Line 80:

	'''Warning:''' Submitting several identical Run Definitions into the same Batch will cause the results from each Run to over-write each other.		'''Warning:''' Submitting several identical Run Definitions into the same Batch will cause the results from each Run to over-write each other.
		+
		+
		+	[[EMK:EMarket User Manual \| Back to User Manual Main Page]]

← Older revision		Revision as of 20:56, 19 November 2012
Line 71:		Line 71:

	==The Run Definition==		==The Run Definition==
		+	The Run Definition Resource determines how EMarket will execute a Run.
		+
		+	More information on how this is created can be found in the [[EMK:Run Window \| Run Window]] section.
		+
		+	Multiple Runs can be executed from a single Run Definition over time. However, a Run Definition can also be changed at any time even when Forecast data has already been produced using the Definition. In other words several differing sets of Results data can be made using the same Run Definition. To ensure that Results can always be interpreted against the exact Run Definition Instance used to produce them, each Run completed in EMarket is assigned a unique Batch number. The Batch number is used to name a sub-folder containing the Run Results data together with a copy of the Run Definition Instance used by the Run. This allows the context of a set of Results to be recreated at a future time (conditional upon certain input data such as Demand profiles being subject to appropriate version control and backup). The numbered sub-folder is located in the Results data folder in the current Working Directory, under the name of the relevant Run Definition.
		+
		+	Note: Where a Batch contains more than one Run Definition, each Run will receive the same Batch Number (but the results will be saved under different Run Definition Resource Names in the Results folder.
		+
		+	'''Warning:''' Submitting several identical Run Definitions into the same Batch will cause the results from each Run to over-write each other.

← Older revision		Revision as of 20:40, 19 November 2012
Line 69:		Line 69:
	#Enters Run details in the '''''System Log'''''		#Enters Run details in the '''''System Log'''''
	#Creates the Run Resource text file capturing the entire context of the Run (effectively a script for the Run) to enable future Run recreation and analysis		#Creates the Run Resource text file capturing the entire context of the Run (effectively a script for the Run) to enable future Run recreation and analysis
		+
		+	==The Run Definition==

← Older revision		Revision as of 20:39, 19 November 2012
Line 62:		Line 62:

	Note: Derivation of the dispatch input data listed above may include the use of the volatility engine through the use of formulae in the Run Definition to express data item values.		Note: Derivation of the dispatch input data listed above may include the use of the volatility engine through the use of formulae in the Run Definition to express data item values.
		+
		+	'''Run Finalisation'''
		+
		+	During Run finalisation EMarket:
		+	#Outputs data in text format
		+	#Enters Run details in the '''''System Log'''''
		+	#Creates the Run Resource text file capturing the entire context of the Run (effectively a script for the Run) to enable future Run recreation and analysis

← Older revision		Revision as of 20:15, 19 November 2012
Line 21:		Line 21:

	==The Run==		==The Run==
		+	A Run is a unique execution of the EMarket model. It produces Forecast distributions of electricity market data from a set of pre-defined modelling assumptions. After production the Forecast data may be used as input into a risk management system for risk assessment or analysed in conjunction with data from other Runs to investigate interesting aspects of the electricity market. The Run uses a Run Definition to identify which input data to use and what form output data is to take. The Run is completely specified by the modelling and data formatting Resources assigned to it in the Run Definition.
		+
		+	A typical EMarket Run has three stages:
		+	#Water Values Calculation
		+	#Dispatch case solution (iterative)
		+	#Run finalisation
		+
		+	'''Calculating Water Values'''
		+
		+	Water Values are used to derive Hydro System Offers at any stage of a Run, based on:
		+	*Reservoir storage levels
		+	*The Offers (marginal costs) of thermal Generators
		+	*The potential reservoir inflows
		+
		+	Typically Water Values are calculated in a single preliminary step at the start of a Run. However, it is possible pre-calculate Water Values as an independent operation, and to instruct EMarket to use these Water Values at run time.
		+
		+	'''Iterative Dispatch'''
		+
		+	Once equipped with a set of Water Values and a valid Definition the Run progresses to solving a series of dispatch cases. Each case requires a single execution of the dispatch engine (and may include execution of the short term river chain optimisation, volatility and Company optimisation engines). A single case represents a basic unitary time period, called a Tick, which can range in duration from one half hour to one week. In most instances Forecast data produced by the Run will contain one value per [[EMK:Entity.Traits \| Entity.Trait]] per Tick. The Tick duration and number of ticks (Forecast duration) for a Forecast are determined in the [[EMK:Run Window \| Run Window]].