ifference between revisions of "EMK:Functional Architecture"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
##Short term river chain optimisation module | ##Short term river chain optimisation module | ||
##Company optimisation module | ##Company optimisation module | ||
− | # | + | #A 'Volatility Engine' which includes: |
+ | ##A '''''Volatility Matrix''''' (incorporating inflow variability) | ||
+ | ##A Monte Carlo series Generator | ||
+ | #A scripting language which includes: | ||
+ | ##A script editor (effectively the EMarket user interface) | ||
+ | ##A script interpreter (controls the system operation) the scripting language underlies all EMarket operations. It is used to: | ||
+ | ###Describe the characteristics of all Resource Instances | ||
+ | ###Control and coordinate the operation of the calculation and volatility engines | ||
+ | ###Control the production and formatting of output data |
Revision as of 08:43, 20 November 2012
This section describes the components which make EMarket work.
Functional Components
- Four 'Calculation Engines:'
- Water Value calculation module
- Dispatch module (SPD simulation)
- Short term river chain optimisation module
- Company optimisation module
- A 'Volatility Engine' which includes:
- A Volatility Matrix (incorporating inflow variability)
- A Monte Carlo series Generator
- A scripting language which includes:
- A script editor (effectively the EMarket user interface)
- A script interpreter (controls the system operation) the scripting language underlies all EMarket operations. It is used to:
- Describe the characteristics of all Resource Instances
- Control and coordinate the operation of the calculation and volatility engines
- Control the production and formatting of output data