Skip to content

Releases: PSLmodels/ParamTools

ParamTools 0.4.1

11 Mar 21:01
2f67c4d
Compare
Choose a tag to compare

ParamTools 0.4.1:

  • Adds several example config piles to MANIFEST.in (#42).

ParamTools 0.4.0

11 Mar 20:30
2fb1437
Compare
Choose a tag to compare

ParamTools 0.4.0 adds:

  • Promotes the tax parameters to be the prominent example in the documentation (#35).
  • Behavior-Responses parameter example and cleaner error messages (#37).
  • Add ability to delete parameter value objects by setting their value to None (#38).
  • Fix a bug where a parameter name specified in the defaults collides with a name used by the Parameters class (#39).
  • Use conda to set up the paramtools development environment and for packaging (#41).

ParamTools 0.3.3

25 Feb 16:42
4d984a3
Compare
Choose a tag to compare

This release improves the format of the README files and adds fields and validator documentation.

ParamTools 0.3.2

21 Feb 19:04
345b98e
Compare
Choose a tag to compare

ParamTools 0.3.2 contains a bug fix that specifies that the data files should be included in the ParamTools package.

ParamTools 0.3.1

21 Feb 18:44
cd93cc0
Compare
Choose a tag to compare

ParamTools 0.3.1 contains a bug fix that stores the example JSON config files in the ParamTools package. This way, the examples work correctly without extra configuration.

ParamTools 0.3.0

15 Feb 15:07
32286b5
Compare
Choose a tag to compare

ParamTools 0.3.0 enables users to more easily access the values of each parameter as NumPy arrays. The shape of the array is determined by the validators set in schema.json and the state of the Parameters instance which can be set via Parameters.set_state. The final piece was to provide a flag array_first which allows the user to specify whether the values should be accessed as NumPy arrays by default or not.

  • ParamTools now requires NumPy to be installed. (#21)
  • Dimension validation information in schem.json is used to define the default array shape for each parameter's value objects. (#22)
  • paramtools.Parameters now has a "state" concept which is used to activate parameter values that lie in the cross section of the dimensions specified with Parameters.set_state. (#23)
  • paramtools.Parameters has an array first option which allows the user to access the parameter values as arrays by default. (#24)

Install with: pip install -U paramtools

ParamTools 0.3.0rc1

12 Feb 16:27
e6595d4
Compare
Choose a tag to compare
ParamTools 0.3.0rc1 Pre-release
Pre-release
  • ParamTools now requires NumPy to be installed. (#21)
  • Dimension validation information is used for converting a list of value objects to an array. (#22)
  • paramtools.Parameters now has a "state" concept which is used for streamlining access to parameter values. (#23)

Install with: pip install paramtools==0.3.0rc1

ParamTools 0.2.0

07 Feb 00:49
d5dd667
Compare
Choose a tag to compare
  • Display the bad value in all error messages. Previously, the bad value was not displayed in type error messages.
  • Validation errors are raised via the paramtools.ValidationError class instead of marshmallow.ValidationError
  • A bug that did not allow array parameters to use choice validation was resolved. Now, ParamTools checks that each element of the "value" array is in the choices list.
  • Automated testing is set up.
  • Pre-commit is used to Black changed code.

ParamTools 0.2.0rc1

01 Feb 15:50
d5dd667
Compare
Choose a tag to compare
ParamTools 0.2.0rc1 Pre-release
Pre-release

This is the first release candidate for the 0.2.0 release:

  • Display the bad value in all error messages. Previously, the bad value was not displayed in type error messages.
  • Validation errors are raised via the paramtools.ValidationError class instead of marshmallow.ValidationError
  • A bug that did not allow array parameters to use choice validation was resolved. Now, ParamTools checks that each element of the "value" array is in the choices list.
  • Automated testing is set up.
  • Pre-commit is used to Black changed code.

ParamTools 0.1.1

23 Jan 15:47
d70feca
Compare
Choose a tag to compare

Features:

  • Use 'title' instead of 'long_name'.
  • Add to_array and from_array to convert data from the Value object structure to an array structure.
  • Add Order object to the spec. This is necessary for the first implementation of the array conversion methods.
  • Revamp the docs to follow the Mozilla WOT API spec structure.
  • Add automating testing with Travis CI.