Preparing OptDataCEP

load_cep_data_provided(region::String)

Loading from .csv files in a the folder ../CEP/data/{region}/ Follow instructions preparing your own data: -region::String: name of state or region data belongs to -costs::OptVariable: costs[tech,node,year,account,impact] - annulized costs [USD in USD/MW_el, CO2 in kg-CO₂-eq./MW_el] -techs::OptVariable: techs[tech] - OptDataCEPTech -nodes::OptVariable: nodes[tech,node] - OptDataCEPNode -lines::OptVarible: lines[tech,line] - OptDataCEPLine for regions:

• "GER_1": Germany 1 node
• "GER_18": Germany 18 nodes
• "CA_1": California 1 node
• "CA_14": California 14 nodes
• "TX_1": Texas 1 node

load_cep_data(data_path::String)

Loading from .csv files in a the folder /data_path/ Follow instructions for the CSV-Files: -region::String: name of state or region data belongs to -costs::OptVariable: costs[tech,node,year,account,impact] - annulized costs [USD in USD/MWel, CO2 in kg-CO₂-eq./MWel]-techs::OptVariable: techs[tech] - OptDataCEPTech - -nodes::OptVariable: nodes[tech,node] - OptDataCEPNode -lines::OptVarible`: lines[tech,line] - OptDataCEPLine

OptVariable{T,N,Ax,L<:NTuple{N,Dict}} <: AbstractArray{T,N}{
data::Array{T,N},
axes::Ax,
lookup::L,
axes_names::Array{String,1}}
type::String

OptVariable is a structure that allows to have a multi-dimensional data-Array that can be indexed using keys. An examplary lookup can be done the following way: optvar['key1','key2']=value. The value can be of any type like e.g. Float64. The OptVariable is used both for data input and output.

• data::Array - includes the optimization variable output in form of an array
• axes_names::Array{String,1}` - includes the names of the different axes and is equivalent to the sets in the optimization formulation
• axes::Tuple - includes the values of the different axes of the optimization variables
• type::String - defines the type of the variable being cv - cost variable - dv -design variable - ov - operating variable - sv - slack variable

 OptDataCEP{region::String,
            costs::OptVariable,
            techs::OptVariable,
            nodes::OptVariable,
            lines::OptVariabl} <: OptData

All not timeseries depending data for the CapacityExpansionProblem is stored in an OptDataCEP struct. OptVariable structs are used to index an element of e.g. .costs['pv','germany',2016,'var','EUR']=value. Depending on the field the value has another type like Number, OptDataCEPLine,...

• region::String: name of state or region data belongs to
• costs::OptVariable: costs[tech,node,year,account,impact] - Number
• techs::OptVariable: techs[tech] - OptDataCEPTech
• nodes::OptVariable: nodes[tech, node] - OptDataCEPNode
• lines::OptVariable: lines[tech, line] - OptDataCEPLine

 OptDataCEPTech{name::String
               tech_group::Array{String,1}
               unit::String
               structure::String
               plant_lifetime::Number
               financial_lifetime::Number
               discount_rate::Number
               annuityfactor::Number
               input::Dict
               output::Dict
               constraints::Dict} <: OptData

The information of the single tech is stored in an OptDataCEPTech struct:

• name: A detailed name of the technology
• tech_group: technology-groups that the technology belongs to. Groups can be: all, demand, generation, dispatchable_generation, non_dispatchable_generation, storage, conversion, transmission
• plant_lifetime: the lifetime of this technologies plant [a]
• financial_lifetime: financial time to break even [a]
• annuityfactor: the annuityfactor is calculated based on the discountrate and the plantlifetime
• discount_rate: discount rate for technology [a]
• structure: node or line depending on the structure of the technology
• unit: the unit that the capacity of the technology scales with. It can be power[MW] or energy[MWh]
• input: the input can be a carrier like e.g. electricity "carrier" => electricity, atimeserieslike e.g."timeseries"=> demand_electricity, or afuellike e.g.fuel: gas`
• constraints: a dictionary with information like an efficiency like e.g. "efficiency"=> 0.53 or cap_eq (e.g. discharge capacity is same as charge capacity) "cap_eq" => "bat_in"

returns techs::OptVariable techs[tech] - OptDataCEPTech

 OptDataCEPNode{name::String,
                value::Number,
                lat::Number,
                lon::Number} <: OptData

The information about the nodes in stored in an OptDataCEPNode struct:

• name
• power_ex existing capacity [MW or MWh (tech_e)]
• power_lim capacity limit [MW or MWh (tech_e)]
• region
• latlon hold geolocation information [°,°]

 OptDataCEPLine{name::String,
                node_start::String,
                node_end::String,
                reactance::Number,
                resistance::Number,
                power::Number,
                circuits::Int,
                voltage::Number,
                length::Number} <: OptData

The information of the single lines is stored in an OptDataCEPLine struct:

• name: Name of the line
• node_start Node where line starts
• node_end Node where line ends
• reactance
• resistance [Ω]
• power_ex: existing power limit [MW]
• power_lim: limit power limit [MW]
• circuits [-]
• voltage [V]
• length [km]
• eff [-]