Citrine

Bug fixes, a bit of refinement, and more bug fixes. No new features for this release, but several corrections to make our interfaces work more smoothly.

Improvements
* We've simplified the predictor classes to better reflect how the Platform operates. All Predictors are Graph Predictors and we've added a new class to represent the nodes of that graph. This should reduce the coding effort for defining and interacting with your models. 844
* We've added a method to the Predictor Collection for asynchronously making a default predictor, if that's more your style. 849

Fixes
* We've corrected some issues with how the SDK was defining ingredient ratio constraints 845
* We've made some unsupported routes a little more obvious 846
* And we've cleaned up test around some deprecated methods 847
* Don't forget that [gemd-python](https://github.com/CitrineInformatics/gemd-python/releases) also fixed some bugs with parsing complex unit expressions and serialization.

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.12.0...v2.15.0

In this release of Citrine Python, we are happy to announce some new changes to make developer's lives easier. We've included new predictor endpoints that allows folks to programmatically fix stale models, simplified some of our code around path construction for `file_link`s, and updated our allowed fingerprint methods in Generative Design. As always, we hope these changes keep you running smoothly.

What's New
* New endpoints to allow users to identify stale predictors (`predictors.is_stale(uid, version=version)`) and retrain stale predictors in-place (`predictors.retrain_stale(uid, version=version)`). This allows users to retrain predictors that have become stale and use single prediction features and Candidate Modification. 843

Improvements
* Simplified our path construction & escaping by centralizing and refactoring methods. 840
* We've updated our documentation and valid fingerprint types accepted in Generative Design strategies. 842

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.11.2...v2.12.0

Today's Citrine Python release is primarily solving a bug that was stinging our users. We're also simplifying our code to make Citrine Python easy to use and easy to learn.

Deprecated
* We've simplified some of our predictor nodes by deprecating the need to designate specific formulation descriptors for the `SimpleMixturePredictor` and `IngredientsToSimpleMixturePredictor` (838) and the capability to designate training data sources on any predictors outside of a `GraphPredictor` (839)

Fixes
* Squashed a bug in the deserialization of predictors leveraging our Chemical Formula Featurizer. 841

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.10.0...v2.11.2

In this release of Citrine Python, we are excited to improve the quality of life for our users and our contributors. We make it easier to reference branches from IDs available in our web app and also include early functionality that allows users to directly ingest a pre-formatted file into GEMD objects. We've also simplified our testing strategy and included a few bug fixes, all in the effort to keep you running (and contributing) smoothly.

What's New
* You can now `get` the root of a branch, rather than the specific version, using the new `BranchCollection.get_by_root_id`. 835
* As alpha functionality, you can now ingest CSV and/or Excel files directly into a GEMD structure, provided the files are formatted according to `gemd-ingest` guidelines. 837

Improvements
* Simplified and centralized testing for faster development. 834

Fixes
* Correction to value types for Chemical Formulae and Molecular Structures. 825
* Ensure labels are included in prediction requests. 836

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.8.0...v2.10.0

With this release of Citrine Python, we are ecstatic to release two major pieces of functionality that have been on the wishlist of many of our users for quite some time. Users with valid Predictors can now submit single prediction tasks and return predictions on just one material. We also now support constraining the ratio of ingredients and labels, allowing users to tackle more complex formulation problems with our optimizer. Not to be outdone, we've also added the capability to use conditional "if" statements within Expression predictors. And if that wasn't enough, we continue to add improvements and simplifications to our python client to keep our users running smoothly.

What's New
* You can now make single prediction calls to a valid Predictor by providing it with a `SinglePredictRequest`, containing candidate information in the form akin to a `DesignMaterial`. The returned object will contain all the values one is able to predict with the Predictor as well as uncertainty. See an example in our [Predictor Documentation](https://citrineinformatics.github.io/citrine-python/workflows/predictors.html#single-predictions). 828, 833
* We now support constraints on the ratio of ingredients in FormulationDesignSpaces. By creating an `IngredientRatioConstraint`, you can constrain the ratio of any combination of ingredients and/or labels to any combination of ingredients and/or labels to be between a minimum and maximum value. We also allow multipliers for each ingredient and label in the numerator or denominator to encode statements such as "constrain 1 part Additive for every 100 parts Solvent". 827

Improvements
* Updated documentation to include the usage of "if" statements inside Expression Predictors. 832
* FileLinks in citrine python have been augmented to include much more additional metadata. Whereas the `dataset.files` endpoint once returned only the filename and url, we now also return created by, created on, and version number fields, among others. 831

Deprecated
* The `FileLink.process` method has been deprecated in favor of UI-driven async ingest methods. 829
* It is no longer needed to designate a `formulation_descriptor` on a `GemTableDataSource` - the descriptor is automatically designated to aid future development. 830

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.2.1...v2.8.0

A small follow up release for [v2.0](https://github.com/CitrineInformatics/citrine-python/releases/tag/v2.0.0) taking care of some clean-up that escaped attention during our big release.

Improvements
* We've exposed `status_detail` for design executions, generative design executions, and PEW executions. (822)

Deprecated
* Accordingly, we've deprecated `status_info` across those and all assets, making it a read-only property which pulls its values from `status_detail`.(822)

Fixes
* Clean-up for now obsolete code that got missed in our previous sweep (821, 823, 824)


**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v2.0.0...v2.2.1