PR software
The important policy of PR is that
all executables, configuration files, scripts and source code
are part of the BABAR (offline) release and
no private/local files should ever
be used to manage PR production.
The exception is not-very-important scripts to look at log files, which are written by you
for your convinience and are not needed in PR operation. However, if such script can be of general use,
PR manage is encouraged to make it part of the release
(talk to PR development team).
As outcome of this policy, three packages are the core of the PR routine operation :
OprProcessingSys, OprConfigSys and OprQaUtils. OprUtils package contains set of script for monitoring PR farms at SLAC.
OprDoc package is used for the web documentation.
- As OPR manager you will be modifying mostly the OprConfXXx.xml
files located in the OprProcessingSys package
- The only other file you might need to edit is the OprShifterConf.xml
(also in OprProcessingSys) that contains
the shifters info (phone numbers and email addresses)
- All other files are managed by PR development team,
and should not be modified (unless you become PR developer)
- Here's a text file with exact directions on how to do
all this
Olya Igonkina
Last modified: Thu Sep 16 13:26:13 PDT 2004