You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NEWS.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,13 @@
1
1
# Release notes
2
2
3
-
## Unversioned
3
+
## Version 0.5.16 (2025-09-24)
4
4
5
5
### Enhancement
6
6
7
7
* Enable reading model results from files by enabling `model::String` being the directory to the saved files instead of `model::JuMP.Model`. Note that the files can be generated by `EnergyModelsGUI.save_results(model::JuMP.model)`.
8
8
* Enhance the descriptive names for nodes having dictionaries with keys of type Resource as in the `MultipleBuildingTypes`-node in `EnergyModelsLanguageInterfaces.jl`.
9
-
* Enhance visualization of plots over OperationalPeriods having a constant non-zero value.
9
+
* Enhance visualization of plots over `OperationalPeriod`s having a constant non-zero value.
10
+
* Improved the cross references in the documentation and added how to show results from a model run.
If you instead (or in addition) want to provide descriptive names through a `Dict`, this can be done as follows
17
+
16
18
```julia
17
19
descriptive_names_dict =Dict(
18
20
:structures=>Dict( # Input parameter from the case Dict
19
21
:RefStatic=>Dict(
20
-
:trans_cap=>"New description for trans_cap",
21
-
:opex_fixed=>"New description for opex_fixed",
22
+
:trans_cap=>"New description for `trans_cap`",
23
+
:opex_fixed=>"New description for `opex_fixed`",
22
24
),
23
25
:RefDynamic=>Dict(
24
-
:opex_var=>"New description for opex_var",
25
-
:directions=>"New description for directions",
26
+
:opex_var=>"New description for `opex_var`",
27
+
:directions=>"New description for `directions`",
26
28
),
27
29
),
28
30
:variables=>Dict( # variables from the JuMP model
29
-
:stor_discharge_use=>"New description for stor_discharge_use",
30
-
:trans_cap_rem=>"New description for trans_cap_rem",
31
+
:stor_discharge_use=>"New description for `stor_discharge_use`",
32
+
:trans_cap_rem=>"New description for `trans_cap_rem`",
31
33
),
32
34
)
33
35
gui =GUI(
@@ -36,9 +38,12 @@ gui = GUI(
36
38
descriptive_names_dict=descriptive_names_dict,
37
39
)
38
40
```
41
+
39
42
The variables for `total` quantities (and their descriptions) can be customized in the same manner (see structure in the `src/descriptive_names.yml` file).
40
43
41
-
It is also possible to ignore certain `JuMP` variables. *E.g.*, ignoring `cap_use` and `flow_in` (in addition to the variable `con_em_tot` which is ignored by default) can be done as follows
44
+
It is also possible to ignore certain `JuMP` variables.
45
+
As an example, `cap_use` and `flow_in` (in addition to the variable `con_em_tot` which is ignored by default) can be ignored through:
You can similarly customize variables that indicates an investment has occured `investment_indicators` the default variables are
51
-
```
52
-
- cap_add
53
-
- trans_cap_add
54
-
- stor_level_add
55
-
- stor_charge_add
56
-
- stor_discharge_add
57
-
```
55
+
56
+
You can similarly customize variables that indicate an investment has occured through the values of the key `:investment_indicators` in the keyword argument `descriptive_names_dict`.
57
+
The default variables are which indicate investments are
58
+
59
+
-``\texttt{cap\_add}`` for all nodes except for [`Storage`](@extref EnergyModelsBase.Storage),
60
+
-``\texttt{stor\_level\_add}`` for all [`Storage`](@extref EnergyModelsBase.Storage) nodes,
61
+
-``\texttt{stor\_charge_\_add}`` for all [`Storage`](@extref EnergyModelsBase.Storage) nodes with charge capacity,
62
+
-``\texttt{stor\_discharge\_add}`` for all [`Storage`](@extref EnergyModelsBase.Storage) nodes with discharge capacity, and
63
+
-``\texttt{trans\_cap\_add}`` for all transmission modes.
Copy file name to clipboardExpand all lines: docs/src/how-to/customize-icons.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
-
# [Customize icons](@idcustomize_icons)
1
+
# [Customize icons](@idhow_to-cust_icons)
2
2
3
3
EnergyModelsGUI provides default icon generation for `Node`s and `Area`s, but these "icons" can be customized by the users.
4
4
You can define an icon based on a `Node``id` or by types.
5
5
To do this you need to specify the `id_to_icon_map` option in the `GUI` function.
6
+
6
7
Say that you want to specify default icons for the types `Source`, `NetworkNode` and `Sink`, and you want to have a special icon for the `Node` with `id``7`, then simply do the following
If the string provided is a full path to a .png file, the GUI will use this file.
24
25
If the string is simply the name of the file (without the .png ending) as above, the GUI will first look for a file in a folder `../icons`.
25
26
If it is not provided here, it will look in the `ext/EMGUIExt/icons/` folder in the EMX repositories.
26
-
If the icon is not found here either, it will fall back to the default icon generation mention earlier (based on simple shapes like circle for `Sink`s and squares for `Source`s and colored by input/output colors).
27
+
If the icon is not found here either, it will fall back to the default icon generation mentioned earlier (based on simple shapes like circle for `Sink`s and squares for `Source`s and colored by input/output colors).
0 commit comments