NAME
     OCSEPMBridge - A daemon to transport parameters from the OCS
     to the EPM

SYNOPSIS
     OCSEPMBridge [-h] [-config <file name>]

DESCRIPTION
     OCSEPMBridge is a daemon process which can be used to  moni-
     tor and transfer the values of parameters in other parameter
     systems such as DRAMA and EPICS and transport  them  to  the
     Electra  Process Monitor (EPM). The EPM is the process table
     employed by the NAOMI system to maintain status valuess.

     The daemon reads a configuration  file  upon  initialisation
     which  instructs it which parameters are to be monitored and
     within which parameter system they  have  their  origin  and
     also which EPM variables their values are to be copied to.

     Updates to the destination parameter values in the  EPM  are
     updated in realtime as monitored values change.

     The EPMDataServer  on  navis.ing.iac.es  should  be  running
     prior to starting this task as it is the EPMDataServer which
     actually affects the update of the EPM once the OCSEPMBridge
     has passed on the request to it.

     Within the OCS, an instance of the OCSEPMBridge is  used  to
     transfer  the  details  of  the TCS parameters necessary for
     NAOMI to calculate the correction to be applied by  the  ADC
     located in the NAOMI system.


OPTIONS
     The command  line  options  that  the  program  accepts  are
     detailed below.

     -h   Print usage information about the application.

     -config <file name>
          The name of the  configuration  file  which  holds  the
          details  of  the  parameters which are to monitored and
          were in the EPM these details should be transferred. By
          default     the     application     uses    the    file
          /wht/etc/OCSEPMBridge.config  in  order  to   configure
          itself.

CONFIGURATION FILES
     All blank lines and lines starting with the # character  are
     ignored by the parser.

     The system can only  currently  be  used  to  monitor  DRAMA
     parameters  and  the  current  syntax  of  the configuration
     reflects that. This may change if there is a need to monitor
     EPICS process variables in addition to DRAMA parameters.

     An example of a configuration file to monitor DRAMA  parame-
     ters in the TCS follows;

     # For DRAMA parameters to be monitored

     # Element 1 : Name of the source parameter system (DRAMA)

     # Element 2 : DRAMA parameter host machine

     # Element 3 : Name of DRAMA parameter to be monitored

     # Element 4 : List of destination EPM Variables, this may be
     a  single  element if monitoring single scalar DRAMA parame-
     ter.

     # Element 5 :  (Optional)  SDS  component  fields  in  DRAMA
     parameter that map to EPM destination parameters

     [list "DRAMA" "TCS@LPAS3" "POSITION"  [list  ParallaticAngle
     DerotatorAngle] [list parallactic rot]]

     # Example of monitoring a single scalar value a DRAMA param-
     eter system

     [list   "DRAMA"    "testParameterServer"    "TestParameter3"
     "aDict"]

     [list   "DRAMA"    "testParameterServer"    "TestParameter2"
     "aDict"]


ENVIRONMENT
     TCLLIBPATH
          This should be set to  include  the  directories  which
          contain  the  WHT  OCS support classes. This is done by
          default from the whtobs account.

SEE ALSO
     EPMDataServer(1)

AUTHOR
     Craige Bevil (cb@ing.iac.es)