-
This should probably be a lot higher
-
A number of presets contain user values for inputs which have been renamed since the preset was created. As a result, these values no longer have any effect on the scenario in ETengine and cause error…
antw updated
11 years ago
-
See quintel/etmodel#1555
-
I created a scenario that is _as green as possible_. (100 % green fuels, green industry, transport, heating etc.) http://beta.energytransitionmodel.com/scenarios/146815
**_Nonetheless, there always se…
-
@wmeyers: can you (make @StijnDellaert) supply the queries in the same format as before?
-
Should be fixed on live too.
-
- 15: households_airconditioning_electricity -> households_cooling_airconditioning_electricity
- 323: households_collective_cooling_heatpump_water_water_ts_electricity -> households_cooling_collective…
-
This is not a bug but a result of the similarity of cooling options in HHs. Perhaps we should display something else? Perhaps we should use different technologies?
-
After the merging of "Input cleanup" pull requests for
- [x] ETsource
- [x] ETmodel
- [x] ETengine
- [x] ETflex
- [x] mechanical_turk
the databases for
- [x] ETmodel
- [x] ETengine?
- [x] ETf…
-
Now their naming is very confusing and very ugly.
@dennisschoenmakers I recall you having ideas of how to rename/restructure input yamls. Assigning to you for the moment.