Some useful Fast Monitoring information for L1 trigger DQ:

adding new L1TFMon modules

New L1TFMon modules should be appended to L1TOepSequences/L1TOepFastMonSequence.*. Once here, L1TFMonXtcApp will pick them up.

updating .ps archive maker

At the end of each run, the production release calls L1TFastMonPostProc (in L1TFMon). This script calls the version of cronmon_live in the release directory /nfs/bbr-nfs03/det/trgmon/trgmon/fastmon/14.4.3/; to modify the .ps archive maker, it is sufficient to:

No further changes need be made. The modifications will take effect the next time L1TFastMonPostProc is run.

The easiest way to test changes is by running a copy of cronmon_live where the variables PSFILESDIR and KUMACPATH are set to appropriate directories in your test release.

For more information, see this HN post.

testing JAS

If you have made changes only to L1TMonTools, it suffices to run RemoteBabarJas and open your copy of L1TMonTools/FastMonHTML/index.html. This will take live data from IR2.

If you have added new histograms and have new .hbook you would like to see, open up four terminal windows, go into a test release, do srtpath, &c. Do the following (one per window):

  1. HbkServer Dot/TestHbookRef your_reference_file.hbook
  2. HbkServer Dot/TestHbook your_data_file.hbook
  3. JasInterfaceServer --name LiveFastMon@Dot/TestHbook --name LiveFastMon-ref@Dot/TestHbookRef -V
  4. BabarJas --connect --startPage file:full_path_to_your_html_file.html
Where, of course, "your_reference_file.hbook", "your_data_file.hbook" & "full_path_to_your_html_file.html" are replaced with the appropriate file names/paths. "" is to be replaced with the machine from which you are running the JasInterfaceServer. "Dot" is just a name and can be replaced with anything you like (within the CORBA spec); so, for example, if you get an error message saying that the name "Dot" has already been allocated, you might try this again with "Dot2".

Nb: There is an idiosyncracy where directory names in .hbook files are limited to 16 (case-insensitive) characters. The live data in IR2 is not subject to this limitation (although the reference data is). The easiest way to work around this is to eschew module names longer than 16 characters.

For more information, see this HN post.

--ks chaisang
23 june 2005