Changeset 1123

Timestamp:

Oct 1, 2012 10:34:46 AM (10 years ago)

Author:

ehanson

Message:

Updated documentation with opisys info

Location:

cssboy_deployment/docs/source

Files:

• configure.rst (modified) (4 diffs)
• install.rst (modified) (1 diff)

cssboy_deployment/docs/source/configure.rst

@@ -25 +25 @@
         ``Switch Workspace...``.
 
-:index:`APS_sr` Project
-===================================
-
-.. warning::  This section needs to be worked out.
-
-..
-        this work has not been done yet, 
-        the screens are not ready, 
-        the instructions are not ready
-
-.. TODO
-        Do NOT forget to update the OPI Search Path instructions, when these screens become available
+:index:`APS System` Project (opisys)
+====================================
+
+Add OPI screens from the APS System as a project.
+
+#. Select menu ``File-->Import ...``
+#. Open ``General`` category,
+   select ``Existing Projects into Workspace``,
+   click ``Next`` button
+#. Click ``Browse ...`` button (in *Import* window)
+#. Navigate to wherever you checked out the ``opisys/`` folder
+#. Click ``Ok`` button
+#. Click ``Finish`` button (in *Import* window)
 
 :index:`synApps` Project
@@ -48 +49 @@
    click ``Next`` button
 #. Click ``Browse ...`` button (in *Import* window)
-#. navigate to ``/APSshare/epics/synApps_5_6/support/``
+#. Navigate to ``/APSshare/epics/synApps_5_6/support/``
    (or ``/usr/local/epics/synAppsSVN/support/`` or wherever)
 #. Click ``Ok`` button
@@ -191 +192 @@
 Change the text in for "OPI Search Path" to this really long string (all one line)::
 
-                /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy | /synApps/autosave/asApp/op/opi | /synApps/busy/busyApp/op/opi | /synApps/calc/calcApp/op/opi | /synApps/camac/camacApp/op/opi | /synApps/dac128V/dac128VApp/op/opi | /synApps/delaygen/delaygenApp/op/opi | /synApps/dxp/dxpApp/op/opi | /synApps/iocStats/op/opi | /synApps/ip/ipApp/op/opi | /synApps/ip330/ip330App/op/opi | /synApps/ipUnidig/ipUnidigApp/op/opi | /synApps/love/loveApp/op/opi | /synApps/mca/mcaApp/op/opi | /synApps/modbus/modbusApp/op/opi | /synApps/motor/motorApp/op/opi | /synApps/optics/opticsApp/op/opi | /synApps/quadEM/quadEMApp/op/opi | /synApps/softGlue/softGlueApp/op/opi | /synApps/sscan/sscanApp/op/opi | /synApps/std/stdApp/op/opi | /synApps/vac/vacApp/op/opi | /synApps/vme/vmeApp/op/opi | /synApps/xxx/xxxApp/op/opi 
+                /synApps/areaDetector/ADApp/op/opi | /synApps/asyn/opi/boy | /synApps/autosave/asApp/op/opi | /synApps/busy/busyApp/op/opi | /synApps/calc/calcApp/op/opi | /synApps/camac/camacApp/op/opi | /synApps/dac128V/dac128VApp/op/opi | /synApps/delaygen/delaygenApp/op/opi | /synApps/dxp/dxpApp/op/opi | /synApps/iocStats/op/opi | /synApps/ip/ipApp/op/opi | /synApps/ip330/ip330App/op/opi | /synApps/ipUnidig/ipUnidigApp/op/opi | /synApps/love/loveApp/op/opi | /synApps/mca/mcaApp/op/opi | /synApps/modbus/modbusApp/op/opi | /synApps/motor/motorApp/op/opi | /synApps/optics/opticsApp/op/opi | /synApps/quadEM/quadEMApp/op/opi | /synApps/softGlue/softGlueApp/op/opi | /synApps/sscan/sscanApp/op/opi | /synApps/std/stdApp/op/opi | /synApps/vac/vacApp/op/opi | /synApps/vme/vmeApp/op/opi | /synApps/xxx/xxxApp/op/opi | opisys/sr | opisys/sr/Gate_Pictures | opisys/sr/absApp | opisys/sr/blmApp | opisys/sr/bmbpm | opisys/sr/bunchIApp | opisys/sr/bunchPurity | opisys/sr/facilitiesApp | opisys/sr/fe | opisys/sr/flagApp | opisys/sr/id | opisys/sr/idbpm | opisys/sr/imagingApp | opisys/sr/iocinfoApp | opisys/sr/mpsApp | opisys/sr/mpsApp/uniq_gen | opisys/sr/operationsApp | opisys/sr/operationsApp/save | opisys/sr/p0fbApp | opisys/sr/psApp | opisys/sr/psApp/noiseMonitoring | opisys/sr/pss | opisys/sr/pss/adl | opisys/sr/scraperApp | opisys/sr/srTuneApp | opisys/sr/tuneApp | opisys/sr/vacApp | opisys/time/injtimeApp | opisys/time/mtimeApp
+
 
 Keep clicking **Ok** until you dismiss all the dialogs. 
@@ -352 +354 @@
 .. _calling.synapps.screens:
 
-Calling synApps screens
-===========================================================
-
-Also, when calling a synApps .opi screen from the instrument or beam line, 
+Calling synApps or System screens
+===========================================================
+
+Also, when calling a synApps or system .opi screen from the instrument or beam line, 
 it is not necessary to use the full path since there is an OPI search path 
 that will locate the screen.  Example, instead of::

cssboy_deployment/docs/source/install.rst

@@ -98 +98 @@
                 on a certain date and may not contain the most recent modifications!
 
+:index:`APS System` Screens (opisys)
+===========================
 
+#. Checkout a snapshot of the screens::
+
+                svn co https://subversion.xray.aps.anl.gov/bcdaext/cssboy_deployment/opisys/ ./opisys
+
+#. Make the script generated screens
+
+        Because there are so many screens (over 4000), many are generated by scripts.
+        To generate these, enter the ``opisys/sr/`` directory and run ``make``.
+        
+        .. caution::
+                Again, Note that these are separate from the development trunk and may 
+                not contain the latest updates!