Citrine

In this release of Citrine Python, we've added some additional functionality that will enable users to share Predictor Evaluation Workflows (and their results) within a Team. We've also removed official support for python 3.6, which reached end of life in late 2021, to keep up with the steady drum beat of software development.

What's New
* Users can now publish Predictor Evaluation Workflows (PEWs) from a project to a team and pull PEWs into other projects within that team. Doing so allows users to view PEW results from any project with access to it and the predictor that was evaluated. https://github.com/CitrineInformatics/citrine-python/pull/784

Deprecation
* Remove official support for python 3.6. https://github.com/CitrineInformatics/citrine-python/pull/783

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.40.0...v1.41.0

In this release of Citrine Python, we are shipping a new tool while paving the way for future functionality. We are proud to introduce the Holdout Set Evaluator, which allows users to evaluate model performance on a user-defined holdout set in lieu of our typical cross validation strategy. We've also included updates to our python SDK that will eventually allow users to select different algorithms in their AutoML Predictors and handle archival of predictors once they have been properly versioned. Both features are still in development for most production deployments, but these changes allow us to test and iterate before full deployment.

What's New
* Preparation for algorithmic selection in AutoML Predictors. The addition of the `estimators` field will eventually allow users to select additional algorithms to be considered during training. Full backend functionality still to come. 780
* Introduction of the Holdout Set Evaluator for generating model error metrics on a customizable holdout set in lieu of typical cross validation. The [`HoldoutSetEvaluator`](https://github.com/CitrineInformatics/citrine-python/blob/984df3d6ff399fe22dd001086b3989e2711f5f17/src/citrine/informatics/predictor_evaluator.py#L138), which can be used in a Predictor Evaluation Workflow alongside or instead of a `CrossValidationEvaluator`, takes a Data Source as an argument that is then predicted with the model during workflow execution. The same set of model performance metrics, such as RMSE and PvA results, can then be calculated and returned in the execution results. 768

Improvements
* Updated reported predictor archival status to prepare for a change with predictor versions. 782

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.37.1...v1.40.0

In this release of Citrine Python, we are shipping internal improvements to both enable further development and allow for smoother debugging in the future. As always, we are constantly improving Citrine Python to be more reliable and flexible to meet your needs.

Improvements
* Additional fields added to predictor reports to support future feature delivery. 778

Fixes
* Introduce `BATCH_SIZE` as a package constant that to control how many objects are registered to the platform at one time. This constant can be extended to debug issues in data service timeouts. 779

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.36.6...v1.37.1

In this release of Citrine Python, we are providing minor fixes and improvements to keep our users running smoothly and building confidently. We've improved our documentation for contributions and included fixes to some of our deprecation warnings brought about by the Teams migration.

Improvements
* Improved documentation for contributions. 775

Fixes
* Correct deprecation warning on `find_or_create_project` and `projects.register` to trigger only when used incorrectly in the Teams context. 774, 777
* Internal fix to default design space creation. 776

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.36.2...v1.36.6

In this release of Citrine Python, we are adding more functionality for the upcoming migration to Teams, including the ability to quickly access user permissions and resources available to a project at the Team level. We've also improved our search functionality around files and performed some additional under-the-hood work to fix bugs and improve performance.

What's New
* New endpoints to allow quick access of a user's permissions on a given Team. Using `team.me()` will allow you to check your permissions within a team with one call! 770
* Added functionality to list the IDs of accessible resources at a Team level. This allows you to see what assets are available to use in their project that have been published from other projects in your team. 769

Improvements
* Improved the way we search for files on our platform by using filters. 772

Fixes
* Minor improvements and bug fixes. 771, 773

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.34.0...v1.36.2

In this release of Citrine Python, we are happy to announce additional configurability of Design Spaces that are created via the `create_default` method. The method, which creates a new Design Space based on a given Predictor configuration, now takes three optional flags: one each to constrain the design space ingredient amounts, label amounts, or ingredient-counts-per-label based on the shape of the training data.

This lets you build your default design space in a number of ways: you can start similar to your training data and expand, or start with a big design space and constrain smaller. All these flags are optional; omitting them will default to "False" resulting in an unconstrained design space. As always, we are also shipping minor bug fixes to keep you running smoothly.

What's New
* Add configurability flags to the `create_default` Design Space method. 767

Fixes
* Minor bug fixes and improvements. https://github.com/CitrineInformatics/citrine-python/pull/766

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v1.33.2...v1.34.0