Citrine

Whats new?

- Ability to list all versions of a table. (289)

Improvements

- The `InorganicDescriptor` is deprecated in favor of the more aptly named `ChemicalFormulaDescriptor`. (288)
- More customizable pagination interface. (289)

Fixes

- The scores "LI" and "EI" are now always referred to by their correct names in variable names and in docstrings. (281)
- `filter_by_template` and `filter_by_spec` are documented more fully. (292)

Citrine v0.15.1 is released! This release patches a deserialization issue in the most recent release and introduces a new seeding utility.

Whats new?

- A seeding utility that separates templates from other data objects (285)

Fixes

- Include `EVScore` in the dictionary of known `Score` types, allowing them to be deserialized (287)

Citrine v0.14.0 is released! This release provides access to the new `citrine.seeding` package which includes various utilities useful for seeding a new deployment.

What's New?
Convenience utilities for seeding a new deployment are now available (https://github.com/CitrineInformatics/citrine-python/pull/283)

Whats new?

- AI Engine: GraphPredictor now supports chaining inputs and outputs for common transfer learning use cases (252)
- Scores have been renamed and a new score (ExpectedValue) was added (233, 280)

Improvements

- AI Engine: Processor is now optional in DesignWorkflows (240, 241)
- Various bug fixes to increase client stability (224, 253, 255, 257, 258, 259, 260, 261, 270, 271)
- Improved documentation and quality of life features for users getting data into the system (229, 235, 238, 244, 248, 249, 251, 274, 278, 279)

Coming Soon

- AI Engine functionality is now explicitly marked ALPHA. Watch for these tags to be removed in upcoming releases, signaling a general availability release. (232)
- GEMD objects now have a `dataset` field (currently `None`) that will soon be populated with the ID of the dataset that contains the object.
- AI Engine: Introducing DataSource configurations to add support for a greater range of data sources for training data, design spaces, etc. in the future. (216)
- Upcoming features related to building tables from GEMD data registered on the platform (226, 228, 234, 236, 237, 202, 245, 247, 250, 256, 263, 264)
- Contributor documentation and experience improvements (227, 239, 243, 254, 262, 265, 269, 273, 275)

Citrine v0.8.0 is released! This release includes significant improvements to the reconstruction of material histories and the serialization and deserialization of the client version of taurus objects.

Improvements
* Material histories will be reconstructed completely, including the ingredients of processes and measurements of materials (https://github.com/CitrineInformatics/citrine-python/pull/223)
* [Taurus v0.6.0](https://github.com/CitrineInformatics/taurus/releases/tag/v0.6.0) is now included, providing enhanced flatten and json support (https://github.com/CitrineInformatics/citrine-python/pull/223)
* Sphinx is now configured to inherit docs from parent classes (https://github.com/CitrineInformatics/citrine-python/pull/197)
* Added documentation of the unit testing system this package uses (https://github.com/CitrineInformatics/citrine-python/pull/201)

Fixes
* Expression predictor documentation had reversed the order of the alias name and the full name (https://github.com/CitrineInformatics/citrine-python/pull/185)
* The session is no longer added to data platform resources that might be json serialized (https://github.com/CitrineInformatics/citrine-python/pull/207)
* The workflow execution controller extracts the right fields from the API response (https://github.com/CitrineInformatics/citrine-python/pull/221)

Changes
* `citrine.attributes` has been deprecated and will be removed in v0.9.0. Attributes should be imported from `taurus.entity.attribute` instead (https://github.com/CitrineInformatics/citrine-python/pull/223)
* Client support for the resources and components of the AI Engine have been marked as `[ALPHA]` to note that their APIs are unstable. They will be omitted from future release notes until they reach beta.

This is a maintenance release that puts version upper bounds on the install dependencies. This will make client installation safer by respecting the possible breaking nature of updates to citrine-python's dependencies when communicated via major version bumps.