Replies: 1 comment
-
|
@ahawkes @alexdewar Comments welcome. Obviously there are more changes than listed here, but this is what I think users should be particularly aware of |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The following guide should be read by all users upgrading from v1.1.0 or earlier. Please read through carefully, as some of the changes may require you to modify your model input files or downstream analysis scripts.
Installation
Virtual environment installation
If you have previously installed MUSE within a virtual environment using the instructions here, you can update MUSE by activating your virtual environment and running
pip install --upgrade muse-os --preThe
--preoption is required as v1.2.0 is currently a pre-release.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
Developer installation
If you have already installed the developer version of MUSE using the instructions here, you can update it to the latest version by doing the following:
MUSE_OSfolder in the terminalgit checkout main, followed bygit pullto get the latest version of the codepip install -e .[dev,doc]As above, if you were previously using Python 3.8, you must set up the installation from scratch using 3.9 or later.
Changes
Model settings
demand_sharehas changed from "new_and_retro" to "standard_demand" (Update examples and tutorials to not use retrofit agents #349). If your model uses retrofit agents, you MUST explicitly specifydemand_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.maximum_iterationshas changed from 3 to 100 (Increase maximum_iterations parameter to 100 #386)Input files
Levelcolumn is no longer required in theTechnodataandCommOutfiles, as this parameter isn't used and never has been (Remove Level parameter from Technodata files #374 and Remove "Level" parameter for outputs and update documentation #377). See updated documentation about this parameter here.ProcessNamecolumn is no longer required in consumption files specified in the consumption_path format. See updated documentation here. 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.Output files
index = true(insettings.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 theindexparameter for any reason (Fix small issues with consumption, supply and prices outputs #412).Model
maximum_iterations> 1.find_equilibriumfunction #407). This will likely affect the results of most models that havemaximum_iterations> 1.minimum_service_factorparameter was previously being applied incorrectly - this has been fixed (Correctly use the minimum service factor #388).settings.tomlfile (with theconstraintskey) were previously being ignored (the model would always revert to the default list of constraints). This has been fixed (Enable customisation of constraints #354).constraintskey, 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"insettings.toml), not the adhoc solver.Other notes
Beta Was this translation helpful? Give feedback.
All reactions