Translations are an aspect of MPS algorithm files that have been left out of the above description so as to make the overall structure clearer.
Translation strings are used in the same way as SLC database alias names - they are used describe an event using meaningful text in a display. MPS displays use translation strings from MPS algorithm files just as the SCP uses SLC database aliases, in preference to the formal mpsl algorithm description itself.
Translation strings may be given in braces after stopper conjunctions and device operand equalities. In a translation string spaces and case are significant. Also they may be no more than 60 characters long.
Here is an example of a translation following each of two stopper conjunctions. Note that a single stopper `conjunction' may consist of only one stopper device operand equality. Translations are attached to stopper conjunctions, rather than whole STOPCNF expressions so that they offer an explanation of the instantaneous state of the machine in an AP's sector rather than a single stopper.
STOPCNF = MPST.AP92.1."PROT" == "UNPRTCTD" &
MPST.AP92.4."PROT" == "UNPRTCTD" {"STOPPER OUT/MOVING"} |
MPST.AP92.5."PROT" == "UNPRTCTD" {"STOPPER OUT/MOVING"}
Translations can also be given for device operand equalities. In this case the translations strings may be attached to a given equality rather than a conjunction. This is so that the translation can be used to describe the individual device being tested. Here is an example of translations used in a NEWRATE clause. The first and third devices have translations associated with them which will be used in control room displays when they trip.
NEWRATE = "ZERORATE"
MPS.AB01.20."12IC" == "OK" {"BSY_12B1_IC TRIPPED"} &
MPS.AB01.20."IC0" == "OK" &
MPS.AB01.20."IC99" == "OK" {"BSY_PC99_IC (at end-of-linac) TRIPPED"}
;