v1.3.0 Release notes

[tsmbland]

Changes

New timeslice_level parameter (#550)

• Users can now specify a timeslice level for each sector using the new timeslice_level parameter (for example timeslice_level = "month").
• This is the level of timeslice granularity over which commodity flows out of a sector are balanced with demand. For example, a user modelling an oil sector may wish to specify that oil supply must match demand on a monthly basis, but not necessarily in every hour (as oil can be stored).
• See documentation for this parameter here. More details can also be found in the pull request description.
• Note: This supersedes the timeslice aggregation feature in previous versions of MUSE. If you have a timeslices.aggregates section in your settings file, this should be deleted, otherwise a warning will be raised.

Default solver (#587)

• The default solver has changed to "scipy" (previously "adhoc").
• If the lpsolver field is left blank for any subsector, a warning will be raised and "scipy" will be used. If you wish to use the "adhoc" solver, you must specify lpsolver = "adhoc".
• Users are encouraged to use the "scipy" solver for all subsectors, unless memory limits are reached (see Memory error for transport model using scipy solver #389)

Bug fixes:

• The processing of the AgentShare parameter (agents file and technodata files) has changed to enforce consistency between the two files (Fix inconsistent reading of agent share names #586). If you receive any new errors like XXXX, please double check that your AgentShare names are consistent between your agents and techodata files. See updated documentation here.

Added support for Python 3.13 (#564)

Deprecated

Outputs (#548)

• The following outputs have been deleted and can no longer be used: "timeslice_supply", "metric_supply", "yearly_supply", "metricy_supply", "timeslice_consumption", "metric_consumption", "yearly_consumption", "metricy_consumption"
• Any attempt to use these outputs will raise an error
• If you need detailed supply/consumption data for any sector, please use 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"

Production methods (#557 and #559)

• The "match" and "costed" options for the dispatch_production parameter have been removed
• Please see here for updated documentation on this parameter

LegacySector (#510)