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: docs/inputs/technodata.rst
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,33 +136,32 @@ InterestRate
136
136
is the technology interest rate (called hurdle rates in other models).
137
137
This is used for the interest used in the discount rate and corresponds to the interest built when borrowing money.
138
138
139
-
Agent_0, ..., Agent_N
140
-
represent the allocation of the initial capacity to the each agent.
141
-
The column heading refers each retrofit agent "AgentShare" as defined in the agents' definition (see :ref:`inputs-agents`).
139
+
Agent0, ..., AgentN
140
+
represent the proportion of initial capacity allocated to each agent.
141
+
Must match AgentShare names specified in the :ref:`inputs-agents` file.
142
+
All agents must be represented in the table.
143
+
If using "New" and "Retrofit" agents, you should create a column with the name of each "Retrofit" agent share.
144
+
If only using "New" agents, you should create a column with the name of each "New" agent share.
142
145
The value corresponds to the ownership of the initial stock, as defined in the :ref:`inputs-existing-capacity` for the starting year of the simulation.
143
-
For example, if an initial boiler stock of 10 PJ is available, this is allocated to each agent according to the "AgentShare".
144
146
145
-
In a one-agent simulation, assuming that the *AgentShare* equals to *Agent_2* for the retrofit agent, the technodata should indicate the stock ownership as follows.
146
-
The modelled agent would own the total 10 PJ of the initial stock of boilers.
147
+
For example, in a one-agent simulation, you should specify the following to indicate full ownership of existing capacity by the agent (assuming an agent share name of "Agent1"):
147
148
148
149
.. csv-table:: Techno-data: AgentShare - 1 agent
149
-
:header: ProcessName, RegionName, Time, ..., Agent_2
150
+
:header: ProcessName, RegionName, Time, ..., Agent1
150
151
151
152
resBoilerElectric, region1, 2010, ..., 1
152
153
resBoilerElectric, region1, 2030, ..., 1
153
154
154
-
In a two-agent simulation, a new column needs to be added for each retrofit agent belonging to the new-retrofit agent pair.
155
-
The column heading refers each retrofit agent "AgentShare" as defined in the agents' definition (see :ref:`inputs-agents`).
156
-
Assuming a split of the initial capacity into 30 \% and 70 \% for each retrofit agent, the model table would be setup as follows.
157
-
The values of the "AgentShare" needs to reflect the demand split represented by the "Quantity" attribute (see :ref:`inputs-agents`),
158
-
to make sure that the initial demand is fulfilled with the initial stock.
155
+
In a two-agent simulation, assuming a 30\% / 70\% split of initial capacity between the two agents, the table would be as follows:
159
156
160
157
.. csv-table:: Techno-data: AgentShare - 2 agents
161
-
:header: ProcessName, RegionName, Time, ..., Agent_2, Agent_4
158
+
:header: ProcessName, RegionName, Time, ..., Agent1, Agent2
162
159
163
160
resBoilerElectric, region1, 2010, ..., 0.3, 0.7
164
161
resBoilerElectric, region1, 2030, ..., 0.3, 0.7
165
162
163
+
Values must sum to 1 for each row of the table.
164
+
166
165
The input data has to be provided for the base year. Additional years within the time
167
166
framework of the overall simulation can be defined. In this case, MUSE would interpolate
168
167
the values between the provided periods and assume a constant value afterwards. The additional
# Release notes for MUSE v1.2.0 (September 19, 2024)
2
+
3
+
These are the main changes in MUSE v1.2.0.
4
+
5
+
Please read carefully if upgrading from an earlier version, as some of the changes may require you to modify your model input files or downstream analysis scripts.
6
+
7
+
## Dropped support for Python 3.8
8
+
9
+
- MUSE is now compatible with Python versions 3.9 to 3.12
10
+
- If you were previously using Python 3.8, you must create a new environment using 3.9 or later. There are instructions on setting up a new environment with the appropriate Python version [here](https://muse-os.readthedocs.io/en/latest/installation/virtual-env-based.html)
11
+
12
+
## Model settings
13
+
14
+
- The default `demand_share` has changed from "new_and_retro" to "standard_demand" ({github}`349`). If your model uses retrofit agents, you MUST explicitly specify `demand_share = "new_and_retro"` for all relevant sectors. If this is left out, the model will try to use the "standard_demand" share and will fail. See updated documentation about this parameter [here](https://muse-os.readthedocs.io/en/latest/inputs/toml.html#standard-sectors).
15
+
- The default value for `maximum_iterations` has changed from 3 to 100 ({github}`386`)
16
+
17
+
## Input files
18
+
19
+
- The `Level` column is no longer required in the `Technodata` and `CommOut` files, as this parameter isn't used and never has been ({github}`374` and {github}`377`). See updated documentation about this parameter [here](https://muse-os.readthedocs.io/en/latest/inputs/commodities_io.html).
20
+
- The `ProcessName` column is no longer required in consumption files specified in the _consumption_path_ format. See updated documentation [here](https://muse-os.readthedocs.io/en/latest/inputs/toml.html#preset-sectors). Users are encouraged to remove this column from their files (summing rows for different processes if necessary), as this more accurately depicts how this data is used in the model.
21
+
22
+
## Output files
23
+
24
+
- We have changed how timeslices are represented in some of the output files ({github}`412`), so this now follows a consistent format across all files. Some of your downstream scripts for loading and analysing these output files may need to be updated.
25
+
- Previously it was necessary to specify `index = true` (in `settings.toml`) for some of the outputs to prevent some important columns from being dropped. This is no longer required, and users should no longer require the `index` parameter for any reason ({github}`412`).
26
+
27
+
## Model
28
+
29
+
- Fixed a bug with the calculation of commodity prices ({github}`418`), which affects all models that have multiple timeslices and `maximum_iterations` > 1.
30
+
- Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked ({github}`407`). This will likely affect the results of most models that have `maximum_iterations` > 1.
31
+
- The `minimum_service_factor` parameter was previously being applied incorrectly - this has been fixed ({github}`388`).
32
+
- Constraints specified in the `settings.toml` file (with the `constraints` key) were previously being ignored (the model would always revert to the default list of constraints). This has been fixed ({github}`354`).
33
+
- We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand ({github}`355`). This is applied by default, however if you are manually overriding the defaults in the settings file with the `constraints` key, you MUST include "demand_limiting_capacity" in this list otherwise this constraint won't be used. Note that this only applies to the scipy solver (`lpsolver = "scipy"` in `settings.toml`), not the adhoc solver.
34
+
- Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices ({github}`304`)
35
+
- Fixed a bug with the weighted_sum decision method ({github}`449`)
36
+
37
+
## Other notes
38
+
39
+
- Please don't use the "metric_supply", "metricy_supply", "timeslice_supply", "yearly_supply", "metric_consumption", "metricy_consumption", "timeslice_consumption" or "yearly_consumption" outputs, as these sometimes give incorrect values and will likely be deleted in the future. You should be able to get everything you need by using the "supply" and "consumption" outputs within each sector, for example (replacing `SECTOR_NAME` with the name of the sector):
Please read carefully if upgrading from an earlier version, as some of the changes may require you to modify your model input files.
6
+
7
+
## Carbon budget module
8
+
9
+
- The bisection method has been fixed, as this was not working as expected before ({github}`483`, {github}`484`). Additionally, a number of default settings have been changed, and parameters renamed. Users must carefully check which parameters are specified in their settings files, as any unspecified parameters will revert to the new defaults. The main changes are as follows:
10
+
-`control_undershoot` / `control_overshoot`: The default has been changed from True to False
11
+
-`method`: The default has changed from `fitting` to `bisection`
12
+
-`method_options.refine_price`: The default has changed from True to False
13
+
-`method_options.resolution`: New parameter
14
+
-`method_options.sample_size`: This parameter no longer applies to the bisection algorithm, and won't be permitted when using that method. Please use `method_options.max_iterations` instead
15
+
-`method_options.tolerance` and `method_options.early_termination_count`: New parameters for the bisection method
16
+
17
+
__Please read the [new documentation page](https://muse-os.readthedocs.io/en/documentation/inputs/toml.html#carbon-market) in full before using a carbon budget__
18
+
19
+
## Default model
20
+
21
+
- A number of changes have been made to the default model that is generated with `muse --model default --copy PATH`. This is mostly to simplify the outputs ({github}`461`)
22
+
23
+
## Tutorials
24
+
25
+
- The tutorials have been simplified and re-ordered ({github}`470`)
26
+
- A tutorial has been added explaining the use of a carbon budget ({github}`486`)
# Release notes for MUSE v1.2.2 (October 28, 2024)
2
+
3
+
These are the main changes in MUSE v1.2.2.
4
+
5
+
## Bug fixes
6
+
7
+
This release fixes several errors in calculations related to the utilization factor, minimum service factor and commodity prices. Interested readers can follow the discussions in the following pull requests:
8
+
9
+
- {github}`368`
10
+
- {github}`518`
11
+
- {github}`534`
12
+
13
+
Developers should pay particular attention to the latter two PRs, to avoid introducing similar mistakes in the future.
# Release notes for MUSE v1.2.3 (November 19, 2024)
2
+
3
+
These are the main changes in MUSE v1.2.0.
4
+
5
+
Please read carefully if upgrading from an earlier version, as some of the changes may require you to modify your model input files.
6
+
7
+
## Log files ({github}`560`)
8
+
9
+
- MUSE will now output two log files to the results folder whenever a simulation is run: one (`muse_info.log`) containing info and debug messages, and the other (`muse_warning.log`) containing warning messages.
10
+
- Users are particularly encouraged to consult the `muse_warnings.log` file after each run, and pay attention to any messages shown.
11
+
12
+
## `MaxCapacityGrowth` parameter ({github}`565`)
13
+
14
+
- The definition of this parameter has changed to compound growth rather than linear growth. It can now be properly interpreted as the maximum growth of the technology per year. See the documentation for this parameter [here](https://muse-os.readthedocs.io/en/latest/inputs/technodata.html)
15
+
- To give an example, if a 5 year time period is being used, a value of 0.5 previously meant that capacity was allowed to grow by 250% over the time period (0.5 x 5 x 100), but with compound growth the limit is now 660% (((1.5 ** 5) - 1) x 100)
16
+
- Users may see results change as a result of this.
17
+
18
+
## Material and Variable costs ({github}`563`)
19
+
20
+
- Fixes errors in the calculation of material and variable costs, particularly in the case of technologies with output quantities not equal to 1. See #563 for details
21
+
- This effects decision metrics, but doesn't directly effect commodity prices. There are known issues remaining in the calculation of commodity prices ({github}`551`, {github}`552`), which will be fixed separately
22
+
23
+
## Minor bug fixes
24
+
25
+
- Fixed an error introduced in v1.2.1 which caused carbon budget simulations to fail if no method options were specified ({github}`539`)
0 commit comments