ixmp v3.1.0 coincides with message_ix v3.1.0.
PR #363: Expand documentation and revise installation instructions.
PR #354: Add
utils.diff(), and allow using filters in CLI command
PR #353: Add functionality for storing ‘meta’ (annotations of model names, scenario names, versions, and some combinations thereof).
ixmp show-versionsincludes the path to the default JVM used by JDBCBackend/JPype.
PR #317: Make
PR #330: Use GitHub Actions for continuous testing and integration.
ixmp v3.0.0 coincides with message_ix v3.0.0.
- Excel input/output (I/O)
ixmp writes and reads items with more elements than the ~10⁶ row maximum of the Excel data format, by splitting these across multiple sheets.
The I/O code now explicitly checks for situations where the index sets and names for an item are ambiguous; see this example for how to initialize and read these items.
- Updated dependencies
The minimum versions of the following dependencies are increased:
dask 2.14 (for reporting)
- Deprecations and deprecation policy
The following items, marked as deprecated in ixmp 2.0, are removed (PR #254):
$HOME/.local/ixmp/as a configuration location. Configuration files are now placed in the standard
clone(). Use shift_first_model_year, keep_solution, and scenario, respectively.
rixmp.legacy, an earlier version of the R interface that did not use reticulate.
Newly deprecated is:
Starting with ixmp v3.0, arguments and other features marked as deprecated will follow a standard deprecation policy: they will be removed no sooner than the second major release following the release in which they are marked deprecated. For instance, a feature marked deprecated in ixmp version “10.5” would be retained in ixmp versions “11.x”, and removed only in version “12.0” or later.
PR #327: Bump JPype dependency to 0.7.5.
PR #320: Add CLI command ixmp show-versions to print ixmp and dependency versions for debugging.
PR #314: Bulk saving for metadata and exposing documentation API
PR #304: Add CLI command
ixmp solveto run model solver.
PR #303: Add dims and units arguments to
PR #270: Include all tests in the ixmp package.
PR #212: Add
Model.initialize()API to help populate new Scenarios according to a model scheme.
PR #267: Apply units to reported quantities.
PR #264: Implement methods to get and create new subannual timeslices.
ixmp v2.0.0 coincides with message_ix v2.0.0.
Support for Python 2.7 is dropped as it has reached end-of-life, meaning no further releases will be made even to fix bugs.
See PEP-0373 and https://python3statement.org.
ixmp users must upgrade to Python 3.
Configuration for ixmp and its storage backends has been streamlined.
See the ref:Configuration section of the documentation for complete details on how to use
ixmp platform add register local and remote databases.
To migrate from pre-2.0 settings:
…pointed to a directory containing database properties (.properties) files.
All Platform configuration is stored in one ixmp configuration file, config.json, and manipulated using the
ixmp platformcommand and subcommands.
Platformconstructor accepts the name of a stored platform configuration.
Different storage backends may accept relative or absolute paths to backend-specific configuration files.
…gave a default backend via a file path.
On the command line, use
ixmp platform add default NAMEto set
NAMEas the default platform.
This platform is loaded when
ixmp.Platform()is called without any arguments.
…pointed to a default local database.
ixmp.configalways contains a platform named ‘local’ that is located below the configuration path, in the directory ‘localdb/default’.
To change the location for this platform, use e.g.:
ixmp platform add local jdbc hsqldb PATH.
PR #240: Add
ixmp listcommand-line tool.
PR #225: Ensure filters are always converted to string.
PR #189: Identify and load Scenarios using URLs.
PR #173: Make AppVeyor CI more robust; support pandas 0.25.0.
PR #165: Add support for handling geodata.
PR #232: Fix exposing whole config file to log output.
ixmp 0.2.0 provides full support for
clone() across platforms (database instances), e.g. from a remote database to a local HSQL database.
IAMC-style timeseries data is better supported, and can be used to store processed results, together with model variables and equations.
Other improvements include a new, dedicated
ixmp.testing module, and user-supplied callbacks in
retixmp package using reticulate to access the ixmp API is renamed to
rixmp and now has its own unit tests (the former
rixmp package can be accessed as
Release 0.2.0 coincides with MESSAGEix release 1.2.0.
PR #135: Test
retixmp) using the R
PR #142: Cloning across platforms, better support of IAMC_style timeseries data, preparations for MESSAGEix release 1.2 in Java core.
PR #115: Support iterating with user-supplied callbacks.
PR #130: Recognize
IXMP_DATAenvironment variable for configuration and local databases.
PR #125: Add functions to view and add regions for IAMC-style timeseries data.
PR #123: Return absolute path from
PR #118: Switch to RTD Sphinx theme.
PR #116: Bugfix and extend functionality for working with IAMC-style timeseries data.
PR #111: Add functions to check if a Scenario has an item (set, par, var, equ).
PR #110: Generalize the internal functions to format index dimensions for mapping sets and parameters.
PR #108: Improve documentation.
PR #103: Specify dependencies in setup.py.
PR #88: Connecting to multiple databases, updating MESSAGE-scheme scenario specifications to version 1.1.
PR #80: Can now set logging level which is harmonized between Java and Python.
PR #79: Adding a deprecated-warning for ixmp.Scenario with scheme==’MESSAGE’.
PR #76: Changing the API from
PR #69: Bring retixmp available to other users.
PR #64: Support writing multiple sheets to Excel in utils.pd_write.
PR #61: Now able to connect to multiple databases (Platforms).
PR #58: Add MacOSX support in CI.
PR #52: Add ability to load all scenario data into memory for fast subsequent computation.