Appendix A Glossary
106
binding preference
A Binding Preference is an object that can be evaluated against
instance of a unit class in order to sort the legal bind targets for a unit
requirement into a most preferred order.
binding requirement
A Binding Requirement is an object that can be evaluated against
instances of a unit class to determine which instances of the class are
legal bind candidates for a unit requirement. When attempting to bind
a unit requirement during recipe execution, the entire set of binding
requirements defined on the unit requirement is evaluated against
each potential binding candidate. Units that are unable to meet every
binding requirement defined on the unit requirement are eliminated
as potential binding candidates for the unit requirement.
binding requirement expression
A Binding Requirement Expression, as defined within the Equipment
Editor, evaluates to either a TRUE or FALSE value. An example would
be "TEMPERATURE < 20.3".
check in
Check in creates a new version of a recipe, which is read-only and
designated with a ~Vn suffix (where n is the version number).
Example: Checking in Make_sauce results in the creation of the
Make_sauce~V1 version.
check out
Check out creates an editable WIP (work-in-progress) recipe,
designated with a ~Vn_WIP suffix (where n is incremented by one).
Example: Checking out Make_sauce~V1 results in the creation of
Make_sauce~V2_WIP. Subsequently, when Make_sauce~V2_WIP is
checked in, it will result in the read-only Make_sauce~V2 version.
class-based recipe
A recipe that specifies one or more unit classes for equipment
requirements. The operator will then be required to specify a particular
unit at the time the batch is created.
To Next Page
Loading...
Need help?
General
