Citrine

We are pleased to roll out the latest version of Citrine Python, featuring significant documentation improvements and an important bug fix that enhances overall functionality for managing projects. We will continue to keep our documentation up to date and squashing bugs keep you all running smoothly!

Improvements
* Improvements to our documentation. 972

Fixes
* Bug fix to `find_or_create` and similar methods to respect team locations. 974, 975, 976, 977, 978, 980

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.11.0...v3.11.6

We're excited to announce the latest enhancements to Citrine Python that continue our commitment to providing our users with a robust and efficient experience. In this release, we've focused on improving our table configuration processes and optimizing our ingestion workflows.

As our platform evolves, we are incorporating faster and easier ways for users to define their training sets, and we now connect our power users to those methods. Users can now leverage direct access to our advanced default table definition processes that leverage `GemdQuery` objects for even smoother table builds.

We've also taken steps to ensure that your data ingestion is not just effective, easy to use, with a direct link from data ingestion to training-set builds inside of a project. For those who value up-to-date and clear documentation, we've made corrections and enhancements to ensure that your integration with our SDK is as smooth as possible. Additionally, this release includes several internal improvements aimed at streamlining development, allowing us to consistently deliver the reliability and performance you expect from Citrine.

What's New
* Provide direct access to our latest default table definition methods via `from_query` for constructing a Table Config. 967

Improvements
* Modify compound ingest operation to wait for table build completion 970
* Internal improvements to streamline development 963, 964, 965, 968

Fixes
* Corrections to our documentation 966
* Add `project` argument to ingestion routes to enable table builds in the same call as ingestion 969

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.5.3...v3.11.0

In this release of Citrine Python, we have a few bug fixes to improve our user experience. We've also deprecated the `training_data` field on our sub-predictors, as those have been required to match the root graph predictor for quite some time. And we've been keeping our dependencies in line, to make sure you all can install and maintain your environment smoothly.

Fixes
* Update to dependencies, eliminating warnings. https://github.com/CitrineInformatics/citrine-python/pull/961
* Fix reading file links in Windows environments. https://github.com/CitrineInformatics/citrine-python/pull/950
* Correction to GEM Table creation warning strings. https://github.com/CitrineInformatics/citrine-python/pull/962

Deprecated
* The `training_data` field on sub-predictors has been deprecated, as having a data source distinct from the root graph predictor would fail to register. https://github.com/CitrineInformatics/citrine-python/pull/960

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.4.8...v3.5.3

In this release of Citrine Python, we are excited to now support more ratio-type units, such as `%` and `ppm`, in our GEMD ingestion. And, per usual, continuous updates to address instabilities and keep you running smoothly!

What's New
* We've updated our `gemd-python` dependency to now support % and other ratio expressions as units. `%`, `ppm`, and [other ratios](https://github.com/CitrineInformatics/gemd-python/blob/bb12bd18ffd3d345f5de6f0455df4ba4b7428642/gemd/units/citrine_en.txt#L196-L201) are available here and on our platform. 959

Fixes
* Updated enumerated design spaces to restrict the allowed data value types. 958

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.4.6...v3.4.8

In this version of Citrine Python, we are excited to introduce a pivotal change to the structure of assets on our platform. We know our users want to get every piece of value out of their data and one way to limit the value of your data that is to keep it locked up in silos. As part of the introduction of Data Manager in the Citrine Platform, we have taken Datasets out of Projects and made them assets of a Team, allowing users direct access to all of the data in their Team to leverage in AI Projects.

This introduces non-breaking changes, but our users are encouraged to migrate to new Team-based or Dataset-based endpoints for data management as soon as possible to (A) take advantage of the Data Manager feature on the Citrine Platform and (B) prepare for the eventual removal of Project-based endpoints. For more details on how this will affect your code, see the [Migrating to Use Data Manager](https://citrineinformatics.github.io/citrine-python/FAQ/data_manager_migration.html) guide in the FAQ section of our documentation or reach our to your Citrine support team.

But that's not all we're bringing in this release. We've also updated our Molecular Generation package to leverage SMARTS notation in defining constraints and introduced simpler filtering methods in our listing methods of AI Assets. And as always, we are keeping our code up to date to maintain data security and keep our users running smoothly!

What's New
* New endpoints and deprecation warnings are introduced to support the use of the Data Manager feature. The key change is that newly registered Datasets are now assets of Teams rather than Projects. We have included new collection methods at the Team and Dataset level to account for this, while also adding deprecation warnings for Project-level collections that will be no longer supported in v4.0. For more details on how this will affect your code, see the [Migrating to Use Data Manager](https://citrineinformatics.github.io/citrine-python/FAQ/data_manager_migration.html) guide in the FAQ section of our documentation or reach our to your Citrine support team. #947, 949, 951, 952, 953, 956

Improvements
* Updates to our Generative Molecular Design package to use SMARTS format for con straining the substructure in a generative design execution 939
* A simpler filtering strategy for listing Predictors and Design Spaces 947

Fixes
* Fix to our PyPi Deployment 957
* Internal maintenance and fixes 945, 946, 948, 953

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.2.11...v3.4.6

In this version of Citrine Python, we are excited to introduce a pivotal change to the structure of assets on our platform. We know our users want to get every piece of value out of their data and one way to limit the value of your data that is to keep it locked up in silos. As part of the introduction of Data Manager in the Citrine Platform, we have taken Datasets out of Projects and made them assets of a Team, allowing users direct access to all of the data in their Team to leverage in AI Projects.

This introduces non-breaking changes, but our users are encouraged to migrate to new Team-based or Dataset-based endpoints for data management as soon as possible to (A) take advantage of the Data Manager feature on the Citrine Platform and (B) prepare for the eventual removal of Project-based endpoints. For more details on how this will affect your code, see the [Migrating to Use Data Manager](https://citrineinformatics.github.io/citrine-python/FAQ/data_manager_migration.html) guide in the FAQ section of our documentation or reach our to your Citrine support team.

But that's not all we're bringing in this release. We've also updated our Molecular Generation package to leverage SMARTS notation in defining constraints and introduced simpler filtering methods in our listing methods of AI Assets. And as always, we are keeping our code up to date to maintain data security and keep our users running smoothly!

What's New
* New endpoints and deprecation warnings are introduced to support the use of the Data Manager feature. The key change is that newly registered Datasets are now assets of Teams rather than Projects. We have included new collection methods at the Team and Dataset level to account for this, while also adding deprecation warnings for Project-level collections that will be no longer supported in v4.0. For more details on how this will affect your code, see the [Migrating to Use Data Manager](https://citrineinformatics.github.io/citrine-python/FAQ/data_manager_migration.html) guide in the FAQ section of our documentation or reach our to your Citrine support team. #947, 949, 951, 952, 953

Improvements
* Updates to our Generative Molecular Design package to use SMARTS format for constraining the substructure in a generative design execution 939
* A simpler filtering strategy for listing Predictors and Design Spaces 947

Fixes
* Internal maintenance and fixes 945, 946, 948, 953

**Full Changelog**: https://github.com/CitrineInformatics/citrine-python/compare/v3.2.11...v3.4.4