Comments (2)
Different levels of detail
Design | Feature 1 | Feature 2 |
---|---|---|
Simplest | Total capacity | Total flow (not considering vintage efficiencies) |
Complicated | Vintage capacity | Vintage flow (directly considering vintage efficiencies) |
Compact | Vintage capacity | Total flow (indirectly considering vintage efficiencies) |
By vintage efficiencies, we mean both production efficiencies (represented by cost parameters in the obj) and conversion efficiencies (used in conversion balances).
The above table serves as a summary and will be elaborated later.
Design 1: simplest formulation
A year index is added to all the existing variables and parameters, and sets for temporal structures. It is needed for the economic representation.
This means, as shown by the below table, we will replace all
For brevity, the rest of the changes in definitions are omitted. We will also update all sets for assets and flows, as they can change per year.
Sets for Temporal Structures
Name | Description | Elements | Superset | Notes |
---|---|---|---|---|
Milestone years | ||||
In-commission milestone years for asset |
||||
Years before milestone year |
||||
In-commission milestone years before milestone years |
||||
Representative periods (rp) within year |
|
|||
Timesteps blocks within a representative period |
|
Parameters
omitted for now
Variables
omitted for now
Objective function
To be added:
- fixed cost for storage energy
weightssee next commentdecommission for existing capacitiesdecommission variables
Note we use lots of tuples for summation because those tuples are the indice domains of the relevant variables, which is needed for implementation. Otherwise you would get an variable "undefined" error. Maybe in the documentation it is better to use simpler summations, i.e., to sum over the entire sets instead of subsets.
Constraints
We would have to change every constraint since we are adding indices, but the two below are the most relevant.
Maximum Output Flows Limit
For conversion, producer, and storage without binary method
Balance Constraint for Conversion Assets
Design 2: complicated formulation
Objective function
To be added:
- fixed cost for storage energy
weightssee next commentdecommission
Constraints
Maximum Output Flows Limit
For conversion, producer, and storage without binary method
Balance Constraint for Conversion Assets
Design 3: compact formulation
Objective function
Here
Constraints
Maximum Output Flows Limit
For conversion, producer, and storage without binary method
Balance Constraint for Conversion Assets
This constraint is the same as in Design 1. However, since it is a compact formulation from Design 2, we should carefully choose
from tulipaenergymodel.jl.
Economic representation
For economic representation we modify the cost parameters in the objective function.
Investment costs
Use this parameter instead of
where salvage value is
and where annualized cost is
Weights for operational cost parameters
Multiply this weight that only depends on operation year
from tulipaenergymodel.jl.
Related Issues (20)
- Rename `rep_periods_data.id` to `rep_periods_data.rep_period` for consistency HOT 2
- Update documentation with max/min energy outgoing flow for assets
- Use the original assets and flows profiles table HOT 5
- run_scenario for connection or other convenience functions
- Move timing from run_scenario to EnergyProblem function
- Merge all profiles-* files into one
- EU benchmark files are too big, store somewhere else HOT 2
- Accept default of missing timeframe and partition tables
- Apply BestieTemplate.jl HOT 1
- Time creating dataframes et al. separately from reading CSV
- Split `profile_name` in the `profiles_table` HOT 3
- Create a meaningful year data for the Norse Case
- Create a site (web or new repo) for the whole pipeline documentation
- Define as input the `resolution` input data in the `rep_periods_data` from somewhere in the pipeline
- Improve user friendliness of the output of the @show of the energy_problem HOT 3
- Test `TimeStruct.jl` package to handle the flexible time resolution in the model
- [BUG] - Change aggregation function for the max/min energy outgoing flow for assets
- Add remote url fix to readme.dev
- Fix readme.dev to our fork workflow HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tulipaenergymodel.jl.