... | ... | @@ -10,7 +10,7 @@ The input data file (1st of July 2020 version) is described in this video: [Inpu |
|
|
|
|
|
The Backbone model is instructed by the modelsInit.gms file (a model definition file) in the input data folder. This file sets e.g. the temporal structure of the model. It often just points to a specific model version that is described by another file (e.g. scheduleInit.gms). This way it is easier to change between different model definition versions. There are templates for different model versions in the Backbone/defModels folder. Here is one-hour video describing the contents of scheduleInit.gms: [Model definition file tutorial video](https://drive.google.com/file/d/1QDL4LHzwU3Ecnv3HID4x8aQVEr8Bd--J/view?usp=sharing)
|
|
|
|
|
|
## 3. Some basic input data elements explained
|
|
|
## 3. Some basic Input Data XLSX elements explained
|
|
|
|
|
|
### 3.1. Minimum requirements for creating an electricity grid (with demand and transmission capacities)
|
|
|
|
... | ... | @@ -25,7 +25,16 @@ The minimum elements for an electricity grid are: |
|
|
|
|
|
#### 3.1.1. Minimum requirements for an electricity market (to be updated)
|
|
|
|
|
|
### 3.2. Minimum requirements for power plant units creating only electricity or heat (to be updated)
|
|
|
### 3.2. Minimum requirements for a power plant unit using a fuel to produce electricity
|
|
|
|
|
|
Once again, using InputData_5Unit_2Node.xlsx in [Example data sets](Getting-started/Example data sets) as an example.
|
|
|
|
|
|
1) Define units and unittypes on _unittype_, _unit_ and _unitUnittype_. Unittypes are groups of units used mainly for results handling. All parameters are given to units (or unit groups, see 3.8. Groups).
|
|
|
2) On _p_gnu_io_ define from which node the unit inputs from (fuel) and which node it outputs to (elec) (=each unit is defined on two rows). The capacity in MW can be set for output, input or both (if e.g. capacity for output is defined, efficiency is used for input capacity). Set conversion coefficient (_conversionCoeff_) to "1" as default.
|
|
|
3) On _p_unit_ set _availability_ to "1" and define _op00_ and _op01_ as the limits for operating shares, e.g. if the unit can operate at 40-100 % of maximum capasity, set _op00_=0,40 and _op01_=1,00. Define also _eff00_ and _eff01_ for corresponding unit efficiencies, e.g. for 0,57 at 40% and 0,60 at 100%, set _eff00_=0,57 and _eff01_=0,60.
|
|
|
4) On _effLevelGroupUnit_ select efficiency conversion method for each unit for each efflevel. (Amount of efflevels is defined in scheduleInit.gms.) Read more about efficiency methods on [Unit Efficiency Approximations (somewhat) Explained](Advanced-modelling/Unit Efficiency Approximations (somewhat) Explained) or use DirectOnLP as default.
|
|
|
5) That's all you really need.
|
|
|
6) To include some costs for using fuels, list fuels in _commodity_ and set a price for using fuel node on _ts_PriceChange_ (if you use changing price time series, note to use _price change_ not _price_ as values). You may also like to add emissions associated with fuel use on _emission_ and _p_nEmission_ (+ CO2 taxes on _p_gnPolicy_).
|
|
|
|
|
|
### 3.3. Combined heat and power (CHP) units (to be updated)
|
|
|
|
... | ... | @@ -60,7 +69,9 @@ _ts_influx_ (hydro reservoirs, waste storages etc.) |
|
|
|
|
|
- if the node has spontaneous influx that can stored, use positive influx for the node to indicate this.
|
|
|
|
|
|
### 3.7. Reserves
|
|
|
### 3.7. Reserves (to be updated)
|
|
|
|
|
|
### 3.8. Groups (to be updated)
|
|
|
|
|
|
|
|
|
|