Citrine

This release includes improvements to Data Object management and documentation updates.

**What’s New:**
* Several helper methods have been added allowing users to easily look up asset ownership information (https://github.com/CitrineInformatics/citrine-python/pull/525)
* Support for batch deletion of GEMD objects is now available via `project.gemd_batch_delete([uuid.UUID('DATA_OBJECT_ID')])` (https://github.com/CitrineInformatics/citrine-python/pull/526)
* Documentation support for the new Design Workflow routes is live (https://github.com/CitrineInformatics/citrine-python/pull/527)

**Improvements:**
* Predictor Evaluation documentation has been rearranged for clarity (https://github.com/CitrineInformatics/citrine-python/pull/500)

**Fixes:**
* `CategoricalConstraint` has been renamed to `AcceptableCategoriesConstraint` in the documentation to reflect recent code changes. (https://github.com/CitrineInformatics/citrine-python/pull/528)

** What's new:**

- Some terms have been renamed for clarity and consistency (523). In all cases the existing term is still valid, but if used will result in a warning and a prompt to use the new term.
- The bounds of a ScalarRangeConstraint are now specified with `lower_bound` and `upper_bound`, and they are specified as inclusive/exclusive with `lower_inclusive` and `upper_inclusive`.
- CategoricalConstraint is now AcceptableCategoriesConstraint.
- The maximum number of candidates an EnumeratedProcessor can process is now `max_candidates`.
- A new predictor evaluation metric has been introduced: "fraction of variance explained," commonly known as `R^2` (524).

**Improvements:**

- Improved documentation around sharing and deleting datasets (518).

**What's new:**

- A method was added that constructs a default Predictor Evaluation Workflow a predictor id.
- `TableBuildAlgorithm` now supports an optional `algorithm` parameter that specifies which algorithm to use when generating a Table Configuration from a sample material history.

**Improvements:**

- The `update` method can be used on data objects and templates (https://github.com/CitrineInformatics/citrine-python/pull/516)
- `DesignExecution`s have a `version_number` that behaves like it did on `WorkflowExecution` (https://github.com/CitrineInformatics/citrine-python/pull/517)


**Fixes:**

- The parameter type docstring for `attribute_contstraints` has been corrected (https://github.com/CitrineInformatics/citrine-python/pull/513)


**Deprecated**

- The `lower_bound` and `upper_bound` optional parameters for `ScalarMinObjective` and `ScalarMaxObjective` have been removed (https://github.com/CitrineInformatics/citrine-python/pull/509).
To apply a constraint, please use the `ScalarRangeConstraint` instead.

**What's new:**

- A new interface for interacting with design workflows (502). Design workflows can now be created and inspected through the `DesignWorkflowCollection`, and executions are contained in a `DesignExecutionCollection`. Design workflow executions have a `.candidates` [method](https://github.com/CitrineInformatics/citrine-python/blob/master/src/citrine/resources/workflow_executions.py#L82), which returns structured `DesignCandidate` objects instead of a JSON blob. Design candidates are paginated for easy access. The old method of retrieving design candidates, `.results`, still functions and is now paginated as well.
- Added unique name support for datasets (512). A dataset can optionally be given a globally unique name, which makes retrieving that dataset faster.


**Improvements:**

- Added exact range bounds to csv columns (503). This information is filled in automatically by the server when processing a CSV file.
- Reorg and fix of documentation, especially documentation on how to get started with citrine-python (510, 507, 508, 506).


**Fixes:**

- Fix type hint for categorical constraint (515). This allows categorical constraints to be used in design workflows.


**Deprecated**

- Descriptors without units have been deprecated (411). Please include units when defining all RealDescriptors. If the value is dimensionless, use an empty string as the units.
- The unused `threshold` parameter has been removed from ChemicalFormulaDescriptor (411).

This release includes two new features: the ability to check for updates to predictors and the ability to create more expressive product design spaces.

**What's new:**

- Added the ability to check for [predictor updates](https://github.com/CitrineInformatics/citrine-python/pull/499/files). This can be used to detect the existence of new training data, which can then be used to update the predictor.
- A new feature of [product design spaces](https://github.com/CitrineInformatics/citrine-python/pull/497): subspaces! A product design space can now be defined as the product of _other_ design spaces as well as univariate dimensions. This makes the product design space more expressive and capable of solving a wide variety of problems. For example, a typical mixing process can now be represented as a product of a formulation design space, to capture the ingredients that can be mixed together, and univariate dimensions to describe the parameters of the mixing process.

**Improvements:**

- Improved [documentation](https://github.com/CitrineInformatics/citrine-python/pull/493) of formulation design spaces and constraints
- Client and documentation [version](https://github.com/CitrineInformatics/citrine-python/pull/495) are now synchronized in a single `__version__.py` file.
- Several bug fixes (492 491 501)