gibney$:[handbook]pcs_testshot.mem

General interest -- ipcs events:  (01-Nov-2004)
-------------------------------
    Running simulation shots (or any other shots) on the pcs requires
    that certain vms-based programs are actively communicating with
    the evtmgr program on epicsrv.  To prime the pump (as it were):
      o on VMS, start up a shotclock:
          $ setup nstx        !if not already done
          $ shotclock "/big"
      o on rich:
          > usrtest
          Enter ['']:  event nstx_soc 111

    This sequence should cause the shotclock on vms to start
    counting, with the shot number "111" in the display.
    If this does not happen within, say, 20 seconds repeat
    the "event" command, maybe with a different shot number:
          Enter ['']:  event nstx_soc 112

    If this STILL does not work, check
        gibney$:[handbook]ipcs_nstx_restart.mem


======================================================================
======================================================================

PCS simulation cycles:
---------------------
Running a PCS simulation cycle causes the PCS lockserver to
declare an ipcs event "PCS_TESTSHOT" which is received on vms
by batch job found in nstx$:[ppcc.com]pcs_testshot.com.  This
procedure prepares the MDSplus files for new data, then declares
PCS_TESTSHOT_READY which tells the lockserver that it can
proceed with the simulation.

This all happens automatically and does not require any of the
rigamarole described below.


======================================================================
======================================================================

PPCC data acquisition testing:
-----------------------------

To test ppcc data acquisition, possibly in conjunction with
rtc and the pcs using PC10 "Local Cycle" page:

  On VMS:  Make sure that batch procedure ENGINEERING_TESTSHOT
    is active.  Easiest way to check is to execute:
        $ @nstx$:[ppcc.com]submit_testshot_jobs.com

    If jobs are active then all is well.  Otherwise, the procedure
    will start up the job for you.

  On rich (assuming that acq program is running):
             > declare_evt ENGINEERING_TESTSHOT  1234

  VMS procedure will:
    o Declare "rich_SOS":  causes acq and pcs to reset
    o Create MDSplus tree for shot 1234 (for example)
    o Declare "NSTX_SHOTTREE_CREATED":  causes pcs final lockout

  On epics PC10 page:  START

Acq cycle should run and data written to the Engineering tree.