|
Amber Boehnlein
FNAL Computing Division (630) 840-2937 cope@fnal.gov |
There is an html based interface which tool authors should use to define and update parameters for tools
To use this interface to update tool and filter definitions, use the pull down menu to select your tool and then press "go". That will put the current parameters, defaults and range in the text boxes. I hope that you will use the range option when appropriate. You might save some poor triggermeister from a truely embarrassing error.
When your edits are complete, hit "commit".
For a new tool, type the name into the text entry box and fill out the parameters, default values and ranges. Be sure to note (no default) and (no range) if applicable.
If you update the database, you'll need to update.
addpkg trigdb_scripts
rm trigdb_scripts/rcp_files/*.rcp
python trigdb_scripts/oracle_scripts/rcpgen.py
Using the parameters
As part of the release, the not-rcp files named filter.rcp and tools.rcp are dumped into an area under the top level release /rundata/trigconfig/rcp Rather than using your own private version of tools.rcp when a tool is released, it's better to use the database version. Otherwise, your private parameters and the database could be out of sync with predictable consequences. The easiest way to do this is to simply copy the database version from /rundata/trigconfig your test scripts:
cp $SRT_TOP/rundata/trigconfig/tools.rcp .
Where you have to set SRT_TOP by hand to be your release area.
setenv SRT_TOP /mylocal_release
Some day SRT_TOP will be part of d0setwa.
User Support
Carmem Silva is the
designer and implementer of the database and web based pages. Please
report suggestions and problems to her.
| Main Page | Next Episode |