...
You are ready to export your software to production.
From lcls-dev2For EPICS IOC Applications:
- If your application is CRAMmed from lcls-dev2:
- cd to TOP of your Application
- cram push
- Otherwise,
- ssh to the production machine shared account, may need to hope to lcls-prod02 first
.
For EPICS IOC applications:
- cd $EPICS_IOC_TOP/<Application>
- eco
m LaserR1-0-0 -d Laser-R1-0-0
Edit RELEASE file and replace path /afs/slac/g/lcls with /user/local/lcls/
- Use eco to checkout your application
- cd to the TOP of your release
- build your application by typeing "make"
- cd ..
- gmake
- cd $EPICS_IOCS/<nodename>
- For hard iocs
cp - cp -p startup.cmd startup.cmd_bckup
and the edit - edit startup.cmd file and point to the new tagged release
- For soft iocs
- mv bin bin_bckup
and - ln -s ../../iocTop/<subsystem>/<tagged-version>/bin/<OS> bin
Reboot ioc, after mcc has granted permission.-
- Enter a log in the operations elog book by sending email to controls-software-release
- Reboot ioc from network panel, after mcc has granted permission.
Matlab Programs Released to Production:
Step 11: Export ChannelWatcher Config Files
(see the example below)
- ssh iocegr@lcls-builder or ssh physics@lcls-srv01
- export CVSROOT=:ext:luchini@lcls-prod02:/afs/slac/g/lcls/cvs
- cd $TOOLS/ChannelWatcher/config
- cvs update <filename>
- ssh laci@lcls-daemon1
- cd /etc/init.d
- ./st.cw<Subsystem> restart ex) st.cwMG for Magnets
- logout
- Note: if you have the Message Logger up (from lclshome) note the number of pv's that failed to connect to ChannelWatcher.
- Enter a message in the operation elog book by sending email to controls-software-release.