ifference between revisions of "EMK:Preface"
Line 16: | Line 16: | ||
#[[EMK:Regions | Regions Resource]] | #[[EMK:Regions | Regions Resource]] | ||
#[[EMK:Binary Output | Binary Outputs Resource]] | #[[EMK:Binary Output | Binary Outputs Resource]] | ||
+ | |||
The following Input and Output Resources are not mandatory for executing a Run, but can be useful: | The following Input and Output Resources are not mandatory for executing a Run, but can be useful: | ||
− | + | #[[EMK:Schedules | Schedules]] | |
− | + | #[[EMK:Reports | Reports]] | |
− | + | #[[EMK:Output Specs | Output Specifications]] | |
Revision as of 14:27, 14 November 2012
It is possible to use EMarket to create nearly all the Resources required to make a Run. However EMarket does require the following information from external sources:
- The Demand Profile
- Inflow Data
- Any other user-defined time series data (see the File input feature in the Run Window)
EMarket calculates Water Values for Hydro Systems from Schedule and other Resource information. However, it is possible for users to define their own Water Values and have EMarket read these instead. In this case the user-defined Water Value file is also a prerequisite.
Defining a Run
Before creating you first Run or Run Definition you will need to create component Input and Output Resource Instances. While there is no set order for creating these, some are dependent on others and the following order of creation is suggested:
- Grid Resource
- Generator Resources
- Companies Resource
- Connections Resource
- Regions Resource
- Binary Outputs Resource
The following Input and Output Resources are not mandatory for executing a Run, but can be useful: