Comments (3)
It looks like Diego has created a file called "how-to-use.md" with some of this information.
Ah wait that's in the Docs - anyway it can be re-used for the readme if we want.
from tulipaenergymodel.jl.
Correct! It is for the documentation; we might want to have only one file with this information, so we need to update it in one file in case of changes. Then, we just need to reference the file with the information in the markdown files. @abelsiqueira What do you think? any best practice here?
from tulipaenergymodel.jl.
I suggest having a small README with the bare information (the list I have above). It should be around 50 lines at most, I imagine. In the README you link to the places with more detailed information. For instance, you can say add to the README something like
Example:
data = read("input.esdl") model = create_model(data) solution = solve_model(model)For more information check the [tutorial](link to tutorial page on documentation).
The snippet is short enough to be useful for people who know what they're doing. Other users can check the tutorial for more info.
from tulipaenergymodel.jl.
Related Issues (20)
- Improve _parse_rp_partitions to reflect more general usage
- Change construct_dataframes to use input data frames
- Change capacity for storage asset to charging and discharging capacities
- Update citation.cff file HOT 2
- Align terminology with ESDL
- Change from_asset/to_asset or from/to for consistency
- Update the outputs with storage investment on energy variable (v^{inv_energy}_{a})
- Update the documentation with investment methods for energy storage assets
- Use TulipaIO instead of reading CSV
- Add a repo checklist to README.DEV
- Change Symbol to String
- Create argument to function that create DB connection to allow a name to be given
- Use the input schema again
- Add the dual solutions to `energy_problem.dataframes[:highest_in_out]`
- Create the new parameter and update the input files for the use of a tighter formulation for storage assets
- Create the new variables and constraints for the use of a tighter formulation for storage assets HOT 1
- Update the documentation (formulation and tutorial/how-to) with the use of a tighter formulation for storage assets HOT 2
- Rename the variables and constraints dataframes in the model
- Possibly rename rep_periods_mapping HOT 1
- [BUG] - Model errors when a storage asset is `investable==false` but `storage_method_energy==true`
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.