CFT Offline Monitoring

Michael Friedman

Contents

Procedure About the executable Notes on how to run

Results What output there is and how to access it:

Root files Run quality database

Other sources of information Unresolved questions

Procedure

The executable David Lam (dlam@fnal.gov) wrote a framework executable,

cftofflmon, which examines raw data files and outputs information about CFT/CPS performance.This executable can be found (on clued0) in /work/nd-clued0/dlam/test2/cft_offline_mon/.

I modified this executable to enable it to work with SAM datasets instead of locally stored files. My version of the executable is available in /work/mithra-clued0/mwfriedm/cftoffline/sambuild/cft_offline_mon/.

The README file in that directory includes documentation on the changes I made. This file is also available at http://www-clued0.fnal.gov/~mwfriedm/notes/README.

Notes on how to run

See http://www-clued0.fnal.gov/~mwfriedm/notes/ That page duplicates some, but not all, of the information in this

presentation. David Lam’s executable does not produce output that can be directly

input into the database; the above website has information about the executables I wrote to take care of that.

Comments I am working backwards from run 177676 to run 173071 (the shutdown

in February). At first, I analyzed 200 events from every raw data file for a given run.

The file transfer time was making each run take about 15 hours to process. Beginning with run 176727, I changed this to 2000 events per file for only every tenth file from a given run. This change improved processing time drastically.

Results

Three places to look for the data I have accumulated On my website:

http://www-clued0.fnal.gov/~mwfriedm/cftofflmon.html In the run quality database:

http://d0db.fnal.gov/qualitygrabber/qualQueries.html In my disk space:

/work/mithra-clued0/mwfriedm/cftoffline/

What you can expect to find

On my website / in my disk space The table on my website has links to files in my disk

space. All the files for a given run are grouped together in a directory called /work/mithra-clued0/mwfriedm/cftoffline/cft_[run_number]

The useful files are all linked to from the website. At the bottom of the table, there is a description of what each of the files contains. See also next slide.

Output files from each run

CFT/CPS_fired_freq.root: Two root files containing information similar to that monitored online by cft_examine—histograms of occupancy, hit maps, etc.

cft_cps_stats.txt: The raw text output from cftofflmon. Contains information about which individual fibers are dead/hot.

stats_summary.txt: Text file read by a python script that updates the database. On my website, there is a link to the corresponding entry. This link requires the username/password for the database; I have not provided them automatically because I was worried about security.

cft_*.log: Standard output/error from the rund0exe command used to process this run. This file will show you what SAM dataset was used to generate the other results.

cftofflmon.log: Standard error from cftofflmon. Only useful for troubleshooting—not particularly useful for an end user.

cftofflmon.out: Stanard output from cftofflmon. Contains some performance information—also not particularly useful for an end user.

Overall.root

A root file that contains ALL of the information that I have input into the database.

To access this file, either download it from my website, or look for it in /work/mithra-clued0/mwfriedm/cftoffline.

Then start root, open up a TBrowser, open the file, and find the object called myTuple. Use the StartViewer method of myTuple to start up a GUI for interacting with these data. (For information on how to use this GUI, go to http://www-root.fnal.gov/root/class/Day2_files/frame.htm, then look for slide 60—The Tree Viewer Overview)

You can then look at 1 dimensional histograms of each parameter, or 2 dimensional scatter plots of any given paramenter vs. run number, etc. etc.

Example histograms

Here we see a scatter plot of one of the quality parameters plotted vs. run number (from overall.root).

More histograms

Here we see a one dimensional histogram of one of the quality parameters (from overall.root).

Yet more histograms!

Here we see a problem in CFT axial layer 8 for run 176761. Although the histogram is called ‘occupancy,’ it is really a hit map. Real occupancy histograms are also available. (from CFT_fired_freq.root for this run)

The run quality database

Method 1: Go to

http://d0db.fnal.gov/qualitygrabber/qualQueries.html, then scroll to the bottom of the page (Run Quality Parameters Query).

Input the run(s) you want to look at, set detector group to CFT, and click Run.

Method 2: As described a few slides ago, there is a direct link to

the entry for each run off of my website. However, you need the database username/password.

Unresolved questions

What are the criteria for marking a parameter/run GOOD? I’ve left everything as UNKNOWN.

If you want to search the database for entries with parameters greater than or less than a certain value, you will have trouble. Comparison is done as if values were strings, not numbers.  For example, searching for parameters matching perc%, with

value greater than 5, returns entries of 5-9, but not 10. This is because “10” < “5”, even though 10 > 5.

Likewise searching for values greater than 10 returns entries of 2 and up.

(Note: the % symbol is a wildcard for the database search.)

Future?

To see where I am right now, check my website As of 8-12-03, I had processed 253 runs, still working back

towards the February shutdown. There is also information from before the shutdown that needs to

be entered. Drew Alton has provided me with a list of problems in runs 151,831-170371 and with the tools I need to convert that list into entries in the database. However, I have yet to do this as of 8-12-03.

I should be able to continue working during the school year here at Rice.

Long term possibilities Tom Diehl suggested including the cftofflmon tool in the reco

work that is done by the farms.