The following describes how to test the individual EPICS Extensions applications after deploying them to LCLS production
The following is a list of EPICS applications bundled as EPICS Extensions R.0.5.0:
Extension | Version | Executable |
---|---|---|
alh | R1.2.351.0.0 | /usr/local/lcls/epics/extensions/alh/R1.2.351.0.0/bin/rhel6x86_64/alh |
alh_DB | R1.2.351.0.0 | /usr/local/lcls/epics/extensions/alh/R1.2.351.0.0/bin/rhel6x86_64/alh_DB |
alh_printer | R1.2.351.0.0 | /usr/local/lcls/epics/extensions/alh/R1.2.351.0.0/bin/rhel6x86_64/alh_printer |
caCamcom | R2.0.0 | /usr/local/lcls/epics/extensions/Camcom/R2.0.0/bin/rhel6x86_64/caCamcom |
caSnooper | R2.1.2.30.1.0 | /usr/local/lcls/epics/extensions/caSnooper/R2.1.2.30.1.0/bin/rhel6x86_64/caSnooper |
ChannelWatcher | R3.0.1 | /usr/local/lcls/epics/extensions/ChannelWatcher/R3.0.1/bin/rhel6x86_64/ChannelWatcher |
CWget | R3.0.1 | /usr/local/lcls/epics/extensions/ChannelWatcher/R3.0.1/bin/rhel6x86_64/CWget |
CWput | R3.0.1 | /usr/local/lcls/epics/extensions/ChannelWatcher/R3.0.1/bin/rhel6x86_64/CWput |
edm | R1.12.105B1.2.0 | /usr/local/lcls/epics/extensions/edm/R1.12.105B1.2.0/bin/rhel6x86_64/edm |
eget | R0.0.00.0.1 | /usr/local/lcls/epics/extensions/eget/R0.0.00.0.1/bin/rhel6x86_64/eget |
ezcaVarArrayTest | R3.7.2 | /usr/local/lcls/epics/extensions/labca/R3.7.2/bin/rhel6x86_64/ezcaVarArrayTest |
flatdb | R2.7.00.1.0 | /usr/local/lcls/epics/extensions/VisualDCT/R2.7.00.1.0/bin/rhel6x86_64/flatdb |
fwdCliS | R1.2.6 | /usr/local/lcls/epics/extensions/fwdCliS/R1.2.6/bin/rhel6x86_64/fwdCliS |
gateway | R2.0.6.01.0.1 | /usr/local/lcls/epics/extensions/gateway/R2.0.6.01.0.1/bin/rhel6x86_64/gateway |
iocLogMsgServer | R1.6.0 | /usr/local/lcls/epics/extensions/iocLogMsgServer/R1.6.0/bin/rhel6x86_64/iocLogMsgServer |
msgReceiver | R1.6.0 | /usr/local/lcls/epics/extensions/iocLogMsgServer/R1.6.0/bin/rhel6x86_64/msgReceiver |
parsecasw | R1.0.3.00.1.0 | /usr/local/lcls/epics/extensions/parsecasw/R1.0.3.00.1.0/bin/rhel6x86_64/parsecasw |
probe | R1.1.8.00.1.0 | /usr/local/lcls/epics/extensions/probe/R1.1.8.00.1.0/bin/rhel6x86_64/probe |
procServ | R2.7.01.1.0 | /usr/local/lcls/epics/extensions/procServ/R2.7.01.1.0/bin/rhel6x86_64/procServ |
pvgetx | R0.0.00.0.1 | /usr/local/lcls/epics/extensions/eget/R0.0.00.0.1/bin/rhel6x86_64/pvgetx |
pvputx | R0.0.00.0.1 | /usr/local/lcls/epics/extensions/eget/R0.0.00.0.1/bin/rhel6x86_64/pvputx |
StripTool | R2.5.18.01.0.0 | /usr/local/lcls/epics/extensions/StripTool/R2.5.18.01.0.0/bin/rhel6x86_64/StripTool |
vdct | R2.7.00.1.0 | /usr/local/lcls/epics/extensions/VisualDCT/R2.7.00.1.0/bin/rhel6x86_64/vdct |
VisualDCT.jar | R2.7.00.1.0 | /usr/local/lcls/epics/extensions/VisualDCT/R2.7.00.1.0/bin/rhel6x86_64/VisualDCT.jar |
The PPS/BCS CUD reads a text file that alhCUD emits
alhCUD is looking at PPS PVs and waiting for them to change state, then writes to that text file.
So I changed the PPS access state of the LCLS Injector Vault, and watched an instance of the PPS/BCS CUD to see if the state change showed up on the CUD.
[physics3@lcls-srv01]$ source $EPICS_SETUP/fixed-epics-setup.bash [physics3@lcls-srv01]$ source $EPICS_SETUP/epicsenv-7.0.2-1.0.bash [physics3@lcls-srv01]$ $TOOLS/script/piopreset -t klys -b li22 -u 21 |
[laci@lcls-daemon10]$ source $EPICS_SETUP/fixed-epics-setup.bash [laci@lcls-daemon10]$ source $EPICS_SETUP/epicsenv-7.0.2-1.0.bash [laci@lcls-daemon10]$ $TOOLS/script/doSnoop.bash 10 20 |
CWget [filename] > [output_file]
CWput [output_file_changes]
You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|