Fast Offline QA Histograms

FTPC Fast Offline Histograms

• Use the Offline Automated QA Browser to fetch the latest set of Fast Offline or DST production jobs.


• Compare the "General Hists" and the "Multiplicity Class Hists" to the appropriate set of FTPC reference histograms:
  • Y2007 AuAu
  • Y2006 pp
  • Y2005 CuCu
  • Y2004 AuAu

Online histograms - "Panitkin Plots"

During a run, online histograms are collected for each sub-system. The online histograms give the first indication of detector hardware problems. Therefore it is extremely important to check these histograms in the control room on evp.starp.bnl.gov at the end of each run. They should also be saved so that they are available for future viewing via the RunLog Browser.

A histogram description has 9 arguments:
1 for 1-D, 2 for 2-D histo
histogram name
histogram title
number of bins x-axis
lower bound x-axis
upper bound x-axis
0 for 1-D histos, number of bins y-axis for 2-D histos
0 for 1-D histos, lower bound y-axis for 2-D histos
0 for 1-D histos, upper bound y-axis for 2-D histos

The following histograms are collected for the FTPC (they are on pages 25-27 up until January 3, 2008 when BEMC histograms were added. The FTPC histograms moved to pages 30-32 starting with run 9003070):

Please inform the FTPC group if you observe large scale changes in any of the FTPC histograms.
The plots on page numbers 26 and 27/ pages 31 and 32 starting with run 9003070 are the most important. They must be checked for every run.

Currently the sample histograms shown below are for the dAu 2007 Run 8340066

• page 6:    FTPC event size on a log10 scale
              Contains the event size histograms for TPC, BEMC, FTPC, L3, SVT and TOF
              Args: 1,h11_ftp_evsize,log of FTPC Buffer Size,50,0.,10.,0,0,0

 
• page 7:    FTPC fraction of total event in %
              Contains the event size fraction histograms for TPC, BEMC, FTPC, L3, SVT and TOF
              Args: 1,h105_ftp_frac,FTP Event Size Fraction (%),50,0.,100.,0,0,0

 
• page 8:    FTPC event size on a log10 scale for the last 2 minutes
              Contains the event size vs time histograms for the TPC and FTPC
              Args: 2,h337_ftp_time_size_2min,FTPC Event Size vs time(sec),600,0.,600.,80,0.,8.

 
• page 25/page 30:
               % of FTPC occupied channels
              Args: 1,h49_ftp,FTPC Occupancy (in %),100,0.,100.,0,0,0
  
              FTPC event size on a log10 scale
              Args: 1,h11_ftp_evsize,log of FTPC Buffer Size,50,0.,10.,0,0,0
  
               % of FTPC occupied channels for laser runs
              Args: 1,h51_ftp_OccLaser,FTPC Occupancy (in %) Lasers,100,0.,100.,0,0,0
  
               Total charge in FTPC on log10 scale
              Args: 1,h48_ftp,log of Total FTPC Charge,30,0.,6.,0,0,0
  
               % of FTPC occupied channels for pulser runs
              Args: 1,h50_ftp_OccPulser,FTPC Occupancy (in %) Pulsers,100,0.,100.,0,0,0
• page 26/page 31:  FTPC chargestep histograms
              Args: 1,h109_ftp_west_time,FTPC West timebins,256,-0.5,255.5,0,0,0
              Args: 1,h110_ftp_east_time,FTPC East timebins,256,-0.5,255.5,0,0,0
  
              The chargestep corresponds to the maximum drift time in the FTPC (clusters from inner radius
              electrode) and is located near 170 timebins. This position will change slightly with atmospheric
              pressure. The other features of these plots are due to electronic noise and pile-up background.
  
              If there is no step visible near 170, something is wrong. Please contact an FTPC expert.


• page 27/page 32:
              Args: 2,h338_ftp_west,FTPC West pad charge: pad vs row,10,0.,10.,960,0.,960.
              Args: 2,h339_ftp_east,FTPC East pad charge: pad vs row,10,0.,10.,960,0.,960.
  
              Red areas = hot FTPC electronics
              White areas = dead FTPC electronics
  
              Always check these 2 plots in the first run after an FTPC trip. If new red or white areas show up,
              first check the FTPC anode voltages. If the anode voltage readings are correct, please contact
              an FTPC expert.
  
              On December 17, 2007, Alexei masked out RDO 10 East. On page 27/32 RDO 10 East is now a white area.

documentation

Welcome! You have found the webpage dedicated to providing information and documentation on the FTPC PadMonitor. The FTPCs (Forward Time Projection Chamber) are a key sub-system of the STAR Experiment at RHIC. The PadMonitor is a software program designed to allow for monitoring of FTPC performance. The program can be separated into two basic parts: the GUI (Graphical User Interface) and the data I/O interface. The GUI has been designed using Java with the data I/O interface provided by the Java Native Interface to C and C++ code. This choice of languages reflects the desire to marry cross-platform transportability with legacy code already written for STAR DAQ data. In addition, we hope to be able to run the PadMonitor as a Servlet or Javascript from the Web, allowing collaborators access to view detector performance or issue trigger commands from a distance.

List

 
This page was written by Janet Seyboth on Febuary 10, 2004

Online

FTPC "Online" Calibration Software

The FTPC "online" calibration software is a collection of programs and macros which run on the FTPC
online machines (virgo-run09.starp,cassini-run09.starp) processing either data directly from the event pool or from
a *.daq file.

All the FTPC calibration software is committed to the online/ftpc branch of the STAR CVS reposititory.
Each committed module contains a README file and a doc subdirectory which contain all the pertinent
information regarding the purpose and use of the program and/or macros contained in the module.

The FTPC "online" calibration program library is located on virgo-run09.starp in /data/FtpcOnlineLibrary
and can be used from the ftpccrew account on virgo-run09.starp.


Attention: The FTPC 3-D display software does not run with ROOT_LEVEL 4.04.02

                                                      Programs in the FtpcOnlineLibrary
Calib_Tool:
                      calib_tool creates a graphical user interface which allows the user to interactively analyze
                      the *.root files produced when the daq files from an FTPC laser run are processed
                     with the FTPC "private chain". The FTPC "private chain" produces a special output
                     file when DEBUGFILE is defined in StFtpcClusterMaker and StFtpcTrackMaker.

CardFinder:
                    The CardFinder utilities,PadAnalysisCreate and PadAnalysisWrite, analyze the pads, locate
                    the bad and/or noisy chips and produce lists of the bad electronics.

EvpPoolReader:
                     Reads, processes and displays event(s) from the event pool: /evp/a, /evp/b or
                     the "live" stream (the event which is currently being input into the event pool).
                     Due to firewall restrictions you can only access the event pool and the live stream from the  starp sub-net .
                    Click here for running instructions.
FtpcPadMonitor:
                    padmon is a software program designed for monitoring the FTPC hardware performance.

NoiseFinder:
                   NoiseFinder contains the programs and macros which produce the FTPC online and offline
                  gain tables.
                 Run the NoiseFinder programs GetGain and FindNoise from the FtpcOnlineLibrary
                 on virgo.starp.bnl.gov to create a gain table. The gain table flags out dead
                 and/or noisy pads. The NoiseFinder utility, WriteAmpSlope_cc.so, converts the
                 gain table into an ftpcAmpSlope.C file which is added to the offline data base
                 in the Calibrations_ftpc/ftpcAmpSlope table.

Online_Tool:
                 Online_Tool contains the shell script ftpc_display and the L3 display
                 macros. The ftpc_display shell script provides an interface to FTPC online
                 event processing. An event from the event pool or from a daq file is read in
                and the cluster finding and tracking results are displayed with the 3-D viewer.
                Click here for running instructions.

Overview

This page was updated by Janet Seyboth on January 25, 2001

Reconstruction

FTPC Reconstruction

• Hit Finding

• Tracking

Simulation

FTPC geometry

• ftpcgeo  - FTPC geant geometry definitions

Momentum Resolution

• HF Momentum Resolution Study Simulations about the performance of the FTPCs in a 0.25T magnetic field

Mock Data challenges

• MDC1
  
• MDC2
  
• MDC4
  

FTPC Fast Simulator

• StFtpcFastSimu

FTPC Slow Simulator

• TUNING
  • Sim vs. Real Data - AuAu (behaviour of number of hits-on-track with event multiplicity)
  • Sim vs. Real Data - dAu (behaviour of number of hits-on-track and residuals)
• StRoot/StFtpcSlowSimMaker pdf ps
• ftpcsim - Wen Gong's original stand-alone version
• pams/ftpc/fss -> StRoot/St_fss_Maker: now obsolete  

Status History for FTPC in MDC4

starnew                     new->SL00d
ROOT 3.00.06
bfc.C(#events,"MDC4","input dataset")

Sim vs. Real Data - dAu

Comparison Slow Simulator and Real data dAu Min Bias

The Distribution of the number of hits-on-global-track is NOT the same for Real Data and Simulation with Hijing through the Slow Simulator (?) What happens with all this 10-hit-on-track ? The used Gain Table is not good enough to reproduce the holes?
 
 

FTPC West	FTPC East
AuAu minbias with low multiplicity in comparison with dAu min bias REAL DATA and SIMULATION	AuAu minbias with low multiplicity in comparison with dAu min bias REAL DATA and SIMULATION
REAL DATA	SIMULATION

 

The residuals are much better for Simulation than for Real data. We still need to do something here )-:

 

 

Sim vs. Real Data - AuAu

Comparison Slow Simulator and Real data for AuAu minbias events

The trend with the variation of the number of hits on track with the multiplicity is the same for Real Data and Simulation with Hijing through the Slow Simulator
 
 

FTPC East
	AuAu minbias REAL DATA from Low Multiplicity (red) to High multiplicity (blue)	AuAu minbias SIMULATION from Low Multiplicity (red) to High multiplicity (blue)
FTPC West
	AuAu minbias REAL DATA from Low Multiplicity (red) to High multiplicity (blue)	AuAu minbias SIMULATION from Low Multiplicity (red) to High multiplicity (blue)

 

The residuals are much better for Simulation than for Real data. We still need to do something here )-: