Totem Monitor: User manual

This manual describes version 4.5.

Using the GUI

The GUI consists of three windows: main window, open dialog and canvas layout dialog. When the Monitor is launched, an empty main window appears. In order to open and analyze a data file, click on Open button and invoke the open dialog. The detailed usage of all three windows is described in the following sections.

Main window

The main window consits of the control panel in the bottom of the window and the canvas area with custom plots. The canvas is formed by a grid of pads, each pad shows one plot. To change number of rows and columns in the canvas grid, use buttons in the layout section of the control panel. To change plot displayed by a pad, double click (or alternatively click while holding ctrl key) on the desired pad. The canvas layout dialog opens and you can select the desired plot. For more details consult the dedicated section.

Open dialog

Hardware setup file describes the hardware setup of the run, e.g. which VFATs were present, mappings of VFATs to detectors, etc. For more details, see section of hardware setup file.

Data source information group

Type specifies type of the run. Possible values are listed in the following table

offline for data taking (not for scans), possible to analyze single events
online not yet implemented
generic scan for threshold, pulse, latency and other scans
TrimDAC scan for TrimDAC scan and analysis
no data (DCU) no data are processed, useful for showing DCU graphs, etc.

Data file is the file with raw data (.dat for binary format, .txt for ASCII format).

I2C configuration (only for scans) is file with VFAT registers as they change during scan.

Cycles per configuration and events per cycles (only for scans) are parameters for synchronization of data and I2C configurations. If you enter wrong value, Monitor is likely to issue a warning or an error in the end of processing.

Setup container group

Source directory is the directory with setup information other than I2C configuration. At the moment it is used only for DCU information. You need not fill this field in unless you want to use DCU information. The DCU information is chached by the Monitor run (it is not read again and again from files) and thus if you change a DCU file, you must check Reset box to reset the cache. Alternatively you can switch off and on the whole Monitor program.

TTP test group

This group provides convenient controls to perform VFAT production tests with TTP. Choose a test from the list load settings for test and the program will automatically fill in all the important fields. You can manually set the name of protocol file.

Canvas layout dialog

The left column displays the list (tree) of hardware elements (see the section on hardware configuration file). First, select the element you are interested in. Then, the right column shows list of plots available for the selected hardware element. Select the desired plot and click on OK button (or alternatively double click on your chosen plot).

Hardware setup file

This file describes hardware setup as a tree. For example one Roman Pot contains 10 planes (hybrids), each plane has 4 VFAT chips and each VFAT has 128 channels. The tree is encoded in XML language and everything must be put in between <top> ... </top> tags. Each object (RP plane, VFAT, etc) is represented by a tag and for each tag there is a certain list of histograms available in the Monitor. A tag can have parameters and all of them take parameter ID which corresponds to the ID of the object and is shown in the Monitor. This parameter must be given. Can be specified in decimal or in hexadecimal (with 0x prefix). All available tags and their parameters are summarized in the following table.

object tag comment parameters
VFAT vfat minimal functionality mask_channels, verbose, iid, position
test_vfat all histograms available as above plus scurvefit
Trigger VFAT trigger_vfat  
one silicon detector rp_plane   z, orientation
set of silicon detectors rp_detector_set   doCorrelations
one GEM t2_detector    
set of GEMs t2_detector_set   CluFileName, SaveClusters

VFAT parameters

mask_channels E.g. value of "12,13,56" means to exclude channels 12, 13 and 56 from later analysis.

verbose parameter influences the level of warnings and errors printed. Value 0 means no output, value 255 full output. Use 0 unless you have some suspicion.

By iid parameter one specifies the internal ID (position) of the VFAT within detector. It is used only if the chip is connected to a GEM. The value ranges from 0 to 16 for GEM.

The position parameter is needed since VFAT IDs are not unique and therefor VFAT frames cannot be identified with the use of IDs. The position is the index (from 0 to 63) within a S-link frame, from which the VFAT frame is loaded.

The parameter scurvefit sets the fit options for S-curve fitting. Its value is composed of two parts. No separator is needed, but I suggest a comma though. One part specifies fit range, possible values are full (for full range) or 10\% (for range starting at 10\% of maximum). Second part determines fit option. Possible values are optL, optW and optWW. If any part is omitted (or whole scurvefit parameter is not present), the defaults (full,optL) are used. The defaults can be invoked also by SCurveFit="default".

RP parameters

z gives the z (perpendicular to the Si detectors) position of the plane, in mm.

orientation gives the orientation of the strips. Possible values are u and v.

doCorrelations controls whether the correlation plots (among planes) are built. They occupy a large portion of memory. The possible values are 0 (not built) and 1 (built).

T2 parameters

If SaveClusters is set to 1, a ROOT file called CluFileName with T2 clusterization results will be saved.

A real-life example

    <rp_plane id="1">   
        <test_vfat id="0xc5f2" verbose="0"/>
        <test_vfat id="0xf173" verbose="0"/>      
        <test_vfat id="0xd7f2" verbose="0"/>
        <test_vfat id="0xd772" verbose="0"/>

-- JanKaspar - 19 Aug 2008

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng CanvasLayout.png r1 manage 10.3 K 2008-08-19 - 16:56 JanKaspar  
PNGpng MainWindow.png r1 manage 53.1 K 2008-08-19 - 16:55 JanKaspar  
PNGpng OpenDialog.png r1 manage 17.1 K 2008-08-19 - 16:55 JanKaspar  
Edit | Attach | Watch | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2010-02-16 - JanKaspar
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    TOTEM All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback