Data

Tools

Indexes

Applications

Experiments

Open Sustainable Technology

A curated list of open technology projects to sustain a stable climate, energy supply, biodiversity and natural resources.

Recent Releases of MUSE_OS

MUSE_OS - v1.4.0

https://muse-os.readthedocs.io/en/latest/release-notes/v1.4.0.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 24 days ago

MUSE_OS - v1.4.0

https://muse-os.readthedocs.io/en/latest/release-notes/v1.4.0.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 24 days ago

MUSE_OS - v1.3.3

https://muse-os.readthedocs.io/en/latest/release-notes/v1.3.3.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 3 months ago

MUSE_OS - v1.3.2

https://muse-os.readthedocs.io/en/latest/release-notes/v1.3.2.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 3 months ago

MUSE_OS - v1.3.1

https://muse-os.readthedocs.io/en/latest/release-notes/v1.3.1.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 4 months ago

MUSE_OS - v1.3.0

https://muse-os.readthedocs.io/en/latest/release-notes/v1.3.0.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 5 months ago

MUSE_OS - v1.2.3

https://muse-os.readthedocs.io/en/latest/release-notes/v1.2.3.html

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 5 months ago

MUSE_OS - v1.2.2

October 28, 2024

Installation

If you have previously installed MUSE within a virtual environment, you can update MUSE by activating your virtual environment and running pip install --upgrade muse-os

If you installed MUSE using a different method, please consult the documentation.

Changes

Bug fixes

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:

  • #368
  • #518
  • #534

Developers should pay particular attention to the latter two PRs, to avoid introducing similar mistakes in the future.

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 6 months ago

MUSE_OS - v1.2.2rc1

This release fixes several bugs related to the utilization factor, minimum service factor and the use of timeslices, which were affecting supply outputs and investment decisions. Most models are likely to be affected in some way by these fixes, although for many models these effects will be small. Models using the minimum service factor, and models with timeslice-level constraints (minimum service factor and utilization factor) are most likely to be strongly effected. Interested readers can follow the discussions in #518 and #368

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 6 months ago

MUSE_OS - v1.2.1

The following guide should be read by all users upgrading from v1.2.0. Please read through carefully, as some of the changes may require you to modify your model input files or downstream analysis scripts.

Installation

If you have previously installed MUSE within a virtual environment, you can update MUSE by activating your virtual environment and running pip install --upgrade muse-os

If you installed MUSE using a different method, please consult the documentation.

Changes

Carbon budget module

  • The bisection method has been fixed, as this was not working as expected before (#483, #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:
    • control_undershoot / control_overshoot: The default has been changed from True to False
    • method: The default has changed from fitting to bisection
    • method_options.refine_price: The default has changed from True to False
    • method_options.resolution: New parameter
    • 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
    • method_options.tolerance and method_options.early_termination_count: New parameters for the bisection method

Please read the new documentation page in full before using a carbon budget

Edit 20/10/24: _MUSE will throw an error if no method_options are specified in the toml file (i.e. if you want to use the default option for all parameters). This is a known bug which will be fixed in v1.2.3, but for now please make that at least one method_option parameter is specified in the toml file (e.g. method_options.max_iterations = 5), or explicitly build an empty dictionary by including the following line: [carbon_budget_control.method_options]

Default model

  • 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 (#461)

Tutorials

  • The tutorials have been simplified and re-ordered (#470)
  • A tutorial has been added explaining the use of a carbon budget (#486)

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 7 months ago

MUSE_OS - v1.2.1rc1

The following guide should be read by all users upgrading from v1.2.0. Please read through carefully, as some of the changes may require you to modify your model input files or downstream analysis scripts.

Installation

If you have previously installed MUSE within a virtual environment, you can update MUSE by activating your virtual environment and running pip install --upgrade muse-os --pre

The --pre option is required as v1.2.1 is currently a pre-release.

If you installed MUSE using a different method, please consult the documentation.

Changes

Carbon budget module

  • The bisection method has been fixed, as this was not working as expected before (#483, #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:
    • control_undershoot / control_overshoot: The default has been changed from True to False
    • method: The default has changed from fitting to bisection
    • method_options.refine_price: The default has changed from True to False
    • 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
    • method_options.tolerance and method_options.early_termination_count: New parameters for the bisection method

Please read the new documentation page in full before using a carbon budget

Default model

  • A number of changes have been made to the default model that is generated with muse --model default --copy PATH. This is mostly to have a simpler model with a reduced set of output files (#461)

Tutorials

  • The tutorials have been simplified and re-ordered (#470)
  • A tutorial has been added explaining the use of a carbon budget (#486)

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 7 months ago

MUSE_OS - v1.2.0

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

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:

  • Activate the environment that you used for the developer installation
  • Navigate to your MUSE_OS folder in the terminal
  • Run git checkout main, followed by git pull to get the latest version of the code
  • To update package dependencies, run pip 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

  • The default demand_share has changed from "new_and_retro" to "standard_demand" (#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.
  • The default value for maximum_iterations has changed from 3 to 100 (#386)

Input files

  • The Level column is no longer required in the Technodata and CommOut files, as this parameter isn't used and never has been (#374 and #377). See updated documentation about this parameter here.
  • The ProcessName column 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

  • We have changed how timeslices are represented in some of the output files (#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.
  • 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 (#412).

Model

  • Fixed a bug with the calculation of commodity prices (#418), which affects all models that have multiple timeslices and maximum_iterations > 1.
  • Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked (#407). This will likely affect the results of most models that have maximum_iterations > 1.
  • The minimum_service_factor parameter was previously being applied incorrectly - this has been fixed (#388).
  • 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 (#354).
  • We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand (#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.
  • Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices (#304)
  • Fixed a bug with the weighted_sum decision method (#449)

Other notes

  • 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): 
    [[sectors.SECTOR_NAME.outputs]]
filename = '{cwd}/{default_output_dir}/{Sector}/{Quantity}.csv'
quantity = "supply"
sink = "aggregate"

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 7 months ago

MUSE_OS - v1.2.0rc4

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 --pre

The --pre option 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:

  • Activate the environment that you used for the developer installation
  • Navigate to your MUSE_OS folder in the terminal
  • Run git checkout main, followed by git pull to get the latest version of the code
  • To update package dependencies, run pip 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

  • The default demand_share has changed from "new_and_retro" to "standard_demand" (#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.
  • The default value for maximum_iterations has changed from 3 to 100 (#386)

Input files

  • The Level column is no longer required in the Technodata and CommOut files, as this parameter isn't used and never has been (#374 and #377). See updated documentation about this parameter here.
  • The ProcessName column 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

  • We have changed how timeslices are represented in some of the output files (#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.
  • 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 (#412).

Model

  • Fixed a bug with the calculation of commodity prices (#418), which affects all models that have multiple timeslices and maximum_iterations > 1.
  • Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked (#407). This will likely affect the results of most models that have maximum_iterations > 1.
  • The minimum_service_factor parameter was previously being applied incorrectly - this has been fixed (#388).
  • 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 (#354).
  • We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand (#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.
  • Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices (#304)
  • Fixed a bug with the weighted_sum decision method (#449)

Other notes

  • 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): 
    [[sectors.SECTOR_NAME.outputs]]
filename = '{cwd}/{default_output_dir}/{Sector}/{Quantity}.csv'
quantity = "supply"
sink = "aggregate"

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 8 months ago

MUSE_OS - v1.2.0rc3

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.

Italics indicates a change from v1.2.0rc2

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 --pre

The --pre option 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:

  • Activate the environment that you used for the developer installation
  • Navigate to your MUSE_OS folder in the terminal
  • Run git checkout main, followed by git pull to get the latest version of the code
  • To update package dependencies, run pip 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

  • The default demand_share has changed from "new_and_retro" to "standard_demand" (#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.
  • The default value for maximum_iterations has changed from 3 to 100 (#386)

Input files

  • The Level column is no longer required in the Technodata and CommOut files, as this parameter isn't used and never has been (#374 and #377). See updated documentation about this parameter here.
  • The ProcessName column 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

  • We have changed how timeslices are represented in some of the output files (#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.
  • 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 (#412).

Model

  • Fixed a bug with the calculation of commodity prices (#418), which affects all models that have multiple timeslices and maximum_iterations > 1.
  • Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked (#407). This will likely affect the results of most models that have maximum_iterations > 1.
  • The minimum_service_factor parameter was previously being applied incorrectly - this has been fixed (#388).
  • 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 (#354).
  • We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand (#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.
  • Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices (#304)
  • Fixed a bug with the weighted_sum decision method (#449)

Other notes

  • 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): 
    [[sectors.SECTOR_NAME.outputs]]
filename = '{cwd}/{default_output_dir}/{Sector}/{Quantity}.csv'
quantity = "supply"
sink = "aggregate"

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 8 months ago

MUSE_OS - v1.2.0rc2

Note: v1.2.0rc3 is now available, see here

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 --pre

The --pre option 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:

  • Activate the environment that you used for the developer installation
  • Navigate to your MUSE_OS folder in the terminal
  • Run git checkout main, followed by git pull to get the latest version of the code
  • To update package dependencies, run pip 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

  • The default demand_share has changed from "new_and_retro" to "standard_demand" (#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.
  • The default value for maximum_iterations has changed from 3 to 100 (#386)

Input files

  • The Level column is no longer required in the Technodata and CommOut files, as this parameter isn't used and never has been (#374 and #377). See updated documentation about this parameter here.
  • The ProcessName column 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

  • We have changed how timeslices are represented in some of the output files (#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.
  • 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 (#412).
  • Fixed a bug that caused data to be duplicated when using the "aggregate" sink for sector outputs (#450)

Model

  • Fixed a bug with the calculation of commodity prices (#418), which affects all models that have multiple timeslices and maximum_iterations > 1.
  • Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked (#407). This will likely affect the results of most models that have maximum_iterations > 1.
  • The minimum_service_factor parameter was previously being applied incorrectly - this has been fixed (#388).
  • 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 (#354).
  • We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand (#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.
  • Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices (#304)

Other notes

  • 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): 
    [[sectors.SECTOR_NAME.outputs]]
filename = '{cwd}/{default_output_dir}/{Sector}/{Quantity}.csv'
quantity = "supply"
sink = "aggregate"

Energy Systems - Energy System Modeling Frameworks - Python
Published by tsmbland 9 months ago

MUSE_OS - v1.2.0rc1

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 --pre

The --pre option 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:

  • Activate the environment that you used for the developer installation
  • Navigate to your MUSE_OS folder in the terminal
  • Run git checkout main, followed by git pull to get the latest version of the code
  • To update package dependencies, run pip 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

  • The default demand_share has changed from "new_and_retro" to "standard_demand" (#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.
  • The default value for maximum_iterations has changed from 3 to 100 (#386)

Input files

  • The Level column is no longer required in the Technodata and CommOut files, as this parameter isn't used and never has been (#374 and #377). See updated documentation about this parameter here.

Output files

  • We have changed how timeslices are represented in some of the output files (#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.
  • 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 (#412).

Model

  • Fixed a bug with the calculation of commodity prices (#418), which affects all models that have multiple timeslices and maximum_iterations > 1.
  • Fixed a bug which was preventing the convergence criteria in the MCA algorithm from being properly checked (#407). This will likely affect the results of most models that have maximum_iterations > 1.
  • The minimum_service_factor parameter was previously being applied incorrectly - this has been fixed (#388).
  • 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 (#354).
  • We have added a constraint that limits installed capacity to be no greater than that required to meet peak demand (#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.
  • Fixed a bug with the calculation of LCOE in models that have a utilization factor of zero for some timeslices (#304)

Other notes

  • 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): 
    [[sectors.SECTOR_NAME.outputs]]
filename = '{cwd}/{default_output_dir}/{Sector}/{Quantity}/{year}{suffix}'
quantity = "supply"
sink = "csv"
overwrite = true

Energy Systems - Energy System Modeling Frameworks - Python
Published by alexdewar 9 months ago

MUSE_OS - v1.1.0

What's Changed

Full Changelog: https://github.com/EnergySystemsModellingLab/MUSE_OS/compare/v1.0.2...v1.1.0

Energy Systems - Energy System Modeling Frameworks - Python
Published by dalonsoa over 1 year ago

MUSE_OS - Version release v1.1.0

What's Changed

Full Changelog: https://github.com/EnergySystemsModellingLab/MUSE_OS/compare/v1.0.2...v1.1.0

Energy Systems - Energy System Modeling Frameworks - Python
Published by sgiarols over 1 year ago

MUSE_OS - v1.0.1

What's Changed

New Contributors

Full Changelog: https://github.com/SGIModel/MUSE_OS/commits/v1.0.1

Energy Systems - Energy System Modeling Frameworks - Python
Published by sgiarols about 3 years ago

MUSE_OS - v1.0.0

What's Changed

New Contributors

Full Changelog: https://github.com/SGIModel/MUSE_OS/commits/v1.0.0

Energy Systems - Energy System Modeling Frameworks - Python
Published by sgiarols about 3 years ago