Difference between revisions of "EMO:Data Sources"
| (4 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
*Probable (not actual) constraints are highlighted on the Map and can be viewed in Watch Windows | *Probable (not actual) constraints are highlighted on the Map and can be viewed in Watch Windows | ||
Market Mode is passive: while viewing and reporting Market-sourced information you cannot alter any of the underlying data or the derived Powerflows. There is only one version of Market data for any given Trading Period, and therefore in Market Data Source Mode views are simply identified by date and Trading Period in the '''''[[EMO:Main Window Title Bar|Main Window Title Bar]].''''' | Market Mode is passive: while viewing and reporting Market-sourced information you cannot alter any of the underlying data or the derived Powerflows. There is only one version of Market data for any given Trading Period, and therefore in Market Data Source Mode views are simply identified by date and Trading Period in the '''''[[EMO:Main Window Title Bar|Main Window Title Bar]].''''' | ||
| + | |||
| + | === Scenario Mode === | ||
| + | A scenario is a snapshot of a single Trading Period taken from either Market (historical) or Forecast data. Once saved, the base inputs for a Scenario cannot be changed. However, in this mode any factor influencing the dispatch for the Period can be temporarily altered and an optimal re-dispatch of the period immediately invoked. The result of a re-dispatched Scenario can be saved as a new Scenario and recalled independently at a future date. While in Scenario mode the Main Window title bar carries the Scenario name, which by default contains the date and Trading Period from which the scenario was originally created. | ||
| + | |||
| + | Scenarios require Offers to exist for the Trading Period in order to solve - this can be verified from the Market view before the Scenario is created. | ||
| + | |||
| + | Scenarios provide a very quick and easy way of setting up and doing what-ifs on the market using optimal dispatch solves (like SPD), without being able to add any new entities (though you can turn entities off, for example by zeroing offers for a generator or reducing the capacity of a circuit to zero). To perform multi-period what-ifs or to add new entities (new nodes, demand, generators, circuits, transformers) then you need to go to Forecast mode. The only exception to this is that EMO can create Auto-SFT constraints for a Scenario. | ||
=== Forecast Mode === | === Forecast Mode === | ||
| − | Forecast Mode allows you to view Forecast output using the same viewing and reporting features used in Market Mode. Once created, Forecast data is stored in the Forecast Library and like Market-sourced data, cannot be amended. However, by running many Forecast Definitions is it possible to create multiple, different, Forecasts for the same Trading Period. The '''''Effective Date Range''''' for a Forecast can start in future or the past. Forecasts are identified by the name you give them at definition time, which appears with the "current" forecast date and Trading Period in the Main Window title bar. | + | Forecast Mode allows you to view Forecast output using the same viewing and reporting features used in Market Mode. Once created by running a series of dispatch solves, Forecast data is stored in the Forecast Library and like Market-sourced data, cannot be amended. However, by running many Forecast Definitions is it possible to create multiple, different, Forecasts for the same Trading Period. The '''''Effective Date Range''''' for a Forecast can start in future or the past. Forecasts are identified by the name you give them at definition time, which appears with the "current" forecast date and Trading Period in the Main Window title bar. |
=== Powerflow Case === | === Powerflow Case === | ||
| − | Powerflow Mode displays the results of a Powerflow Case analysis output through the Presentation Interface. Powerflow Cases are defined in a similar way to Forecast Definitions. However, while Forecasts | + | Powerflow Mode displays the results of a Powerflow Case analysis output through the Presentation Interface. Powerflow Cases are defined in a similar way to Forecast Definitions. However, while Forecasts dispatch offers optimally and require Offers data, Powerflow cases execute ''EMarketOffer's'' powerflow engine and use Generation and Demand data as inputs. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | [[ | + | [[Main Page|Home]] |
Latest revision as of 10:00, 11 February 2014
The EMarketOffer Presentation Interface provides four generic data presentation modes, referred to as data sources. These are:
- Market
- Forecast
- Powerflow Case
- Scenario
Market Mode
Market mode is available for any historical day for which EMarketOffer can access data. It is not available for future dates. For the Trading Period under review, Market-sourced data automatically includes the best available:
- Transmission System configuration including Branch Constraints
- Equation Constraints
- Prices
- Load
- Generation
While in Market Mode:
- Powerflows are automatically calculated and displayed on the Map and in Watch Windows
- Probable (not actual) constraints are highlighted on the Map and can be viewed in Watch Windows
Market Mode is passive: while viewing and reporting Market-sourced information you cannot alter any of the underlying data or the derived Powerflows. There is only one version of Market data for any given Trading Period, and therefore in Market Data Source Mode views are simply identified by date and Trading Period in the Main Window Title Bar.
Scenario Mode
A scenario is a snapshot of a single Trading Period taken from either Market (historical) or Forecast data. Once saved, the base inputs for a Scenario cannot be changed. However, in this mode any factor influencing the dispatch for the Period can be temporarily altered and an optimal re-dispatch of the period immediately invoked. The result of a re-dispatched Scenario can be saved as a new Scenario and recalled independently at a future date. While in Scenario mode the Main Window title bar carries the Scenario name, which by default contains the date and Trading Period from which the scenario was originally created.
Scenarios require Offers to exist for the Trading Period in order to solve - this can be verified from the Market view before the Scenario is created.
Scenarios provide a very quick and easy way of setting up and doing what-ifs on the market using optimal dispatch solves (like SPD), without being able to add any new entities (though you can turn entities off, for example by zeroing offers for a generator or reducing the capacity of a circuit to zero). To perform multi-period what-ifs or to add new entities (new nodes, demand, generators, circuits, transformers) then you need to go to Forecast mode. The only exception to this is that EMO can create Auto-SFT constraints for a Scenario.
Forecast Mode
Forecast Mode allows you to view Forecast output using the same viewing and reporting features used in Market Mode. Once created by running a series of dispatch solves, Forecast data is stored in the Forecast Library and like Market-sourced data, cannot be amended. However, by running many Forecast Definitions is it possible to create multiple, different, Forecasts for the same Trading Period. The Effective Date Range for a Forecast can start in future or the past. Forecasts are identified by the name you give them at definition time, which appears with the "current" forecast date and Trading Period in the Main Window title bar.
Powerflow Case
Powerflow Mode displays the results of a Powerflow Case analysis output through the Presentation Interface. Powerflow Cases are defined in a similar way to Forecast Definitions. However, while Forecasts dispatch offers optimally and require Offers data, Powerflow cases execute EMarketOffer's powerflow engine and use Generation and Demand data as inputs.