Recommendation: The topics covered in this article are recommended for experienced automation users. We recommend you have a clear understanding of the distinction between a liquid class and a liquid policy.
Learn more here.
Overview
By default, Synthace will try to match the conditions and parameters of each liquid transfer to a liquid class saved to your device.
If you have predefined liquid classes for the device that you wish to use, you can create liquid policies and rules that override the default planning behaviour and force the use of your existing class.
Once created, you can use these policies in your Synthace workflow to force the use of a pre-existing liquid class. This is called a 'liquid class override'. Specifying a liquid class in your liquid policy will enable Synthace to use your pre-existing liquid classes.
Read on to learn how to create your liquid class overrides.
Creating Liquid Policies with liquid class overrides
First, navigate to the Liquid Policies Inventory and Add a new liquid policy.
Provide a name and description for your policy. We recommend you use the name of the liquid class that you wish to use. This will aid clarity when assigning your policy to liquids in the workflow builder. See here for details on how to do this.
Navigate to the rules tab and begin defining your rule. Click + Add Consequence and select Liquid Class Override from the dropdown menu.
Now simply provide the name of the liquid class that you wish to use in the table. The liquid class override text must match the liquid class name in the vendor software exactly!
Click Add Policy and the new policy you have created will be added to your liquid policy inventory, ready for future use.
Using conditional rules with liquid class overrides
If you have multiple existing classes you wish to use, where the choice of the class depends on a condition then you can configure liquid policy rules to achieve the desired behaviour.
In the "Conditions" section, define the conditions that tell Synthace when to use this rule.
See below for an example.
Read this article to learn more about creating liquid policy rules
Note that there are several limitations to using liquid class overrides in your workflows:
If you wish to use this approach across multiple liquid handlers, you may require multiple policies as the liquid class names may vary between device
The class selected in the override will be used in the aspirate, dispense and mixing steps of any liquid handling planned by Synthace