Overview
Element parameters often use maps with key-value pairs. Take the Aliquot Volume parameter below, for example. This parameter consists of two parts, a Key and a value .
The Key relates to the values in another parameter, for example, the name of the liquid to be aliquot. In the example below, the default key means the volume will be applied to all liquids provided to the aliquot element. We then specify the value of the Aliquot Volume parameter equals 100 ul, for the default liquids. This allows us to map specific values to specific or default keys.
In Synthace, Liquid Names and Tags are used to assign values like concentration to liquids or to define transfer volumes for liquids and tagged groups. Keys are essential to how Synthace elements function—it's crucial that they remain unmodified since changes can affect workflow behavior. This is especially important when creating protocols.
To prevent unintended changes, we've implemented a method to hide these keys while still allowing users to modify their associated values. This protection is vital because, in typical workflows, certain parameters and their associated liquids are critical—changing key values often leads to simulation errors.
To safeguard protocols, we've given protocol creators control over key value visibility. This protects users from simulation errors while still allowing them to update important parameter values in their protocols.
Implementation Steps
Define protocol parameters:
Toggle on the parameters of interest.
Control parameter key visibility using the parameter checkbox
A checkbox is provided next to the value entry field for map parameters.
When this checkbox is toggled on, it adds a value field for the parameter without exposing the key.
The configuration panel will then indicate that the input field is for the concentrations/volumes associated with the hidden key.
Hover over the input field to reveal the source element.
Now, when progressing to the personalization window, you will see the parameter
valuefield, but thekeywill be hidden
This method enhances the robustness of protocols by safeguarding critical keys while still allowing necessary user interactions.
Protocol Integrity: By hiding keys, we prevent accidental changes that could disrupt the workflow.
User Experience: Users can focus on modifying values without the risk of altering essential parameters.