Database Access

How to access database:

• Instantiate StFgtDbMaker ->  StFgtDbMaker *myStFgtDbMaker=new StFgtDbMaker();
• Then get tables ->  StFgtDb * fgtTables = myStFgtDbMaker->getDbTables();
• Now you can go get whatever geometry stuff you might need from StFgtDb.  For example:
  • fgtTables->getPhysicalCoordinateFromGeoId(geoId, &disc, &quad, &layer, &ordinate, &lower, &upper);
  • fgtTables->getGeoIdfromElecCoord(rdo, arm, apv, ch);

Electronic ID Formula:

    if ( apv > 11 ) apv = apv - 2;

    ElectId = channel + 128 * ( apv + 20 * (arm + 6 * ( rdo - 1) ) );

 

General Database Info (from Dmitry)

1. For real .daq files processing, timestamp is taken from event - it cannot be set by user. For example, if event timestamp is XYZ, then db maker will get db entries with time validity spanning from [XYZ - some_time_1] to [XYZ + some_time_2] where some_time1 is the beginTime of the db entry received, and some_time_2 is the beginTime of the next db entry with beginTime > XYZ.

2. DBV option (in chain) only freezes validity range, which means "do not consider calibrations uploaded later than DBVXXYYZZ". This allows to reproduce any past conditions. So, if you set DBV to today's date, you will get latest calibration dataset. If you set it to some past date (e.g. 2010-01-01) then you will get only those datasets which were uploaded before 2010-01-01. So, tables are read using both beginTime and entryTime..

FGT Pedestal Maker, Reader, and Plotter

See Renee's instructions how to create and upload pedestals/status attached
-----------------

I had hoped to write this tutoral once all code was in CVS and I had automated all of the loading and writing scripts. Unfortunately these conditions are only partially fullfilled at this time, so this procedure describes how to make pedestal and status files needed to load to the database:

• mkdir FgtPed
• cd FgtPed
• stardev
• cvs co StRoot/StFgtPool/StFgtRawDaqReader
• cvs co StRoot/StFgtPool/StFgtCosmicTestStandGeom
• cvs co StRoot/StFgtPool/StFgtPedMaker
• cvs co StRoot/StFgtPool/StFgtStatusMaker
• cvs co StRoot/StFgtPool/StFgtQaMakers
• cons
• cvs co StRoot/StFgtPool/StFgtQaMakers/macro/makeFgtPedAndStat.C

You will need to open makeFgtPedAndStat.C and set the database time manually (next step is to automate this).  This timestamp is used to get the correct mapping:

• dbMkr->SetDateTime(20121108,000000);

You also need to set the file and output file name fields at the top, but this is easily done dynamically if you wish.  Next simply run the macro :  root4star -b -q makeFgtPedAndStat.C.  Eight files will be part of the output:

• Filename.FGT-ped-DB.dat
• Filename.FGT-ped-stat-info.txt
• Filename.FGT-ped-stat.pdf
• Filename.FGT-ped-stat.ps
• Filename.FGT-ped-stat.root
• Filename.FGT-ped-stat.txt
• Filename.FGT-stat-DB.dat
• fgtMapDump.csv

The .dat files need to be loaded to the database using the macros

• cvs co StRoot/StFgtUtil/database/macros/write_fgt_pedestal.C
• cvs co StRoot/StFgtUtil/database/macros/write_fgt_status.C
• cvs co StRoot/StFgtUtil/database/macros/fgtPedestal.h
• cvs co StRoot/StFgtUtil/database/macros/fgtStatus.h

Now you need to open each of these macros and set the database time and file input correctly before running via the standard root4star -b -q write_fgt_pedestal.C.

---

Software for computing (making), reading (from file or DB) and plotting pedistals has been written.  The DB functionality is not fully implemented as of Jan 10, 2012.

 

---

Files

The current code for reading and writing pedistals is contained in the following files

$CVSROOT/offline/StFgtDevel/StRoot/StFgtPedMaker/StFgtPedMaker.h
$CVSROOT/offline/StFgtDevel/StRoot/StFgtPedMaker/StFgtPedMaker.cxx
$CVSROOT/offline/StFgtDevel/StRoot/StFgtPedMaker/StFgtPedReader.h
$CVSROOT/offline/StFgtDevel/StRoot/StFgtPedMaker/StFgtPedReader.cxx

An example of using the pedistal maker is in the file

$CVSROOT/offline/StFgtDevel/StRoot/StFgtPedMaker/macro/makeCosmicPeds.C

An example of using the pedistal reader is in the file

$CVSROOT/offline/StFgtDevel/StRoot/StFgtPool/StFgtPedPlotter/macro/plotPedsFromFile.C

An auxillary class to make a nice plot of pedistals is found in the files

$CVSROOT/offline/StFgtDevel/StRoot/StFgtPool/StFgtPedPlotter/StFgtPedPlotter.h
$CVSROOT/offline/StFgtDevel/StRoot/StFgtPool/StFgtPedPlotter/StFgtPedPlotter.cxx

After the software review, it is expected to move these files to StRoot instead of offline/StFgtDevel/StRoot

---

StFgtPedMaker

The StFgtPedMaker is designed to use the FGT online containers in StEvent.  The pedistals are the mean ADC value over all events processed by the chain, while the "RMS" is actually the standard deviation.  Running sums are computed in the StFgtPedMaker::Make function, and the final values are computed in ::Finish member function.  The values can then be written to a file, which contains four columns: (1) geoId of the strip (2) timebin (3) pedistal, i.e. mean ADC (4) RMS, i.e. st. dev.

The pedistal maker has the following user functions to modify the options:

   void setToSaveToFile( const Char_t* filename );
   void setToSaveToDb( Bool_t doIt = 1 );
   void setTimeBinMask( Short_t mask = 0xFF );

To save to file, one uses the "setToSaveToFile" function and passes the filename to which the information should be saved.  The "setToSaveToDb" function is not yet implemented.  It was decided not to allow this functionality in this class, but rather have a decidated macro to upload a text file generated by this class into the DB.  The time bin mask is set via the "setTimeBinMask" function.  All time bins which are flagged "false" in the mask will be ignored.  Note: time bin 0x01 is the 0th time bin, 0x10 is the 4th time bin, etc. 

The status of the strips (e.g. dead, broken, and/or hot strips) is not considered in making the pedistals.  All pedistals are computed for the time bins specified in the time bin mask.  As status of the strips is given by the StFgtStatusMaker/Reader, it is expected that the code querying the StFgtPedReader for a pedistal will also query the StFgtStatusReader for a status of the strip, and then choose to act accordingly.  In this manner, the status does not have to be computed before computing the pedistals, but instead should be computed before using the pedistal information.

---

StFgtPedReader

It was anticipated that all calls for pedistals, in all software, would use the StFgtPedReader.  The StFgtPedReader initially either loads the pedistals from file, or from the database, and holds them in an associative array, allowing both sparse data and for fast look ups.  In future versions, one could change the implimentation to a static array, if one desired faster processing but a larger memory imprint.  The code has the following accessor function, to read the time bine for a given geoId and time bin:

   // accessor: input is geoId and timebin, output is ped and
   // st. dev. (err).  Returns error if pedistal not found for given geoId and timebin
   Int_t getPed( Int_t geoId, Int_t timebin, Float_t& ped, Float_t& err ) const;

One can also set a time bin mask via

   void setTimeBinMask( Short_t mask = 0xFF );

Time bins with bits set to false will be ignored.  The fewer time bins loaded, the faster the initial load and the faster the look up time for each individual geoId afterwards.

The DB interface still needs to be programmed as of Jan 10, 2012.

---

StFgtPedPlotter

This produces a nice plot of the pedistals for a given quadrant (10 APVs).  The procedure is straight forward. See the macro and the code for an example of how this is done.  Note: the ped. plotter gives an example of how to use the ped. reader.

---

Comments

Usually 2,000 are used to compute pedistals.  The amount of time taken by the StFgtPedReader/Maker is significantly less than the amount of time used by the RawMaker to create the FGT containers in the StEvent and read the DAQ file from disk, and therefore can be considered negligible for the present.

An example pedistal file is attached.  This file is from the cosmic test stand, when quadrants 008, 018, 007 were on the top, middle, and bottom possition, respectively.  Plots of typical pedistal RMS can be found on page 1 of the QA plots produced during the cosmic test stand.  The base directory is http://www.star.bnl.gov/protected/spin/sgliske/fgtCosmicQA/, from which you can then select a quadrant, and then select a .pdf file.  The files are named via the quandrant and the time the data was taken.

FGT Simulation

Random notes from email exchanges:

 

A bfc that produces muDsts from simulation files looks like this
root4star -b bfc.C'(10,"MakeEvent,ITTF,NoSsdIt,NoSvtIt,Idst,VFPPVnoCTB,logger,-EventQA,-dstout,tags,Tree,EvOut,analysis,dEdxY2,IdTruth,useInTracker,-hitfilt,tpcDB,TpcHitMover,TpxClu,McAna,fzin,y2012,tpcrs,geant,geantout,beamLine,eemcDb,McEvOut,bigbig,emcY2,EEfs,bbcSim,ctf,-CMuDST,sdt20120501.060500","pp200_QCDprodMBc.fzd")' -q > & Log1

There is  an fzd file in avossen/tmp/4jason/

 

The code is available at
StRoot/StFgtSimulator/
and should also be available as

The bfc to run it is in StRoot/StFgtSimulator/macros/bfc.C
You can run it from the StFgtDevel dir with the following
command line:

%root4star -b
StRoot/StFgtSimulator/macros/bfc.C'(10,"MakeEvent,ITTF,NoSsdIt,NoSvtIt,Idst,VFPPVnoCTB,\
  logger,-EventQA,-dstout,tags,Tree,EvOut,analysis,dEdxY2,\
  IdTruth,useInTracker,-hitfilt,tpcDB,TpcHitMover,TpxClu,\
  McAna,fzin,y2012,tpcrs,geant,geantout,beamLine,eemcDb,\
  McEvOut,bigbig,emcY2,EEfs,bbcSim,ctf,-CMuDST","pp200_QCDprodMBc.fzd")'

 

 

Legend for Status in DB

Strip Status

Status bits are failure states, i.e. status of 0 is good, anything else is bad. Strip status bits are defined as

• bit 1: pedestal out of range (current range is 100-1200 ADC)
• bit 2: RMS out of range (current range is 10-80 ADC)
• bit 3: Fraction of integral near pedestal value (i.e +/- 1 RMS of the pedestal) out of range (current range is 0.6 to 0.95)
• bit 4: not used
• bit 5: APV chip bad (threshold is currently 64 dead strips)
• bit 6: strip not connected

Note, for bit 5, all strips are set to have this bit fail if more than the threshold number of strips on this APV failed the tests corresponding to bits 1-3.

Mapping for Run13

 See
drupal.star.bnl.gov/STAR/event/2012/12/07/fgt-weekly-meeting-0/fgt-run13-daq-cable-mapping

Offline Software

Getting started with plots for the FGT

(some old documentation on how to read MuDSTs: drupal.star.bnl.gov/STAR/blog/avossen/2012/apr/26/how-read-mudsts)
Prepare your libraries
If you're brand new or starting fresh directory for FGT, you'll need to check out some files... This is a list of all the offline FGT software you're likely to need for whatever it is you're working on...
> mkdir mydir
> cd mydir
> cvs co StRoot/RTS
> cvs co StRoot/St_base
> cvs co StRoot/StEvent
> cvs co StRoot/StFgtA2CMaker
> cvs co StRoot/StFgtClusterMaker
> cvs co StRoot/StFgtDbMaker
> cvs co StRoot/StFgtPool
> cvs co StRoot/StFgtRawMaker
> cvs co offline/StFgtDevel/StRoot/StMuDSTMaker

> ln -s offline/StFgtDevel/StRoot/StFgtMuDSTMaker/ StRoot/StFgtMuDSTMaker

The last step is necessary since StFgtMuDSTMaker is not yet in devel.
Make sure you are in the proper STAR version (you want "development") and compile...
> starver dev
> cons

Pick your data
After your libraries installed correctly, pick a daq file for your FGT studies... (If you're using MuDST files this will be different..)
> ls /star/data03/daq/2012/xxx/13xxxyyy
where 13xxxyyy is the run number you want. (If the run number you want isn't there, restore the daq files yourself or ask somebody to do it.)
Before running over data, make sure to run klog to ensure you get a token to communicate with the database..
> klog

>For MuDSTFiles the corresponding #define directive in StFgtPool/StFgtClusterTools/StFgtGeneralBase.h has to be set.

Run over the data
To fill all the plots you want, you'll need to run this command (when sitting in mydir)...
> cd mydir
> root4star -b -q StRoot/StFgtPool/StFgtClusterTools/macros/agvEffs.C'("/star/data03/daq/2012/131/13173068p_rf/st_physics_13173068_raw_202001.root",10,10000,2)' > & output.txt
The above command will attempt to run over 10,000 events from the example daq file, using disc 2 as the disc that is removed for efficiency calculations. Piping the output to file is necessary in order to cut down on running time. On average, 10,000 events takes ~45 minutes as long as you use an output file.

Look at the plots
The agvEffs.C macro will output some .root files...
-clusterEff.root
-clusterPics.root contains visual "pictures" of the first 1000 clusters found in the daq file.
-pulses.root counts pulses in the electronics etc
-signalShapes.root contains a whole heck of a lot of plots... To see exactly all that is put into signalShapes.root, take a look at StFgtClusterTools/StFgtGenAVEMaker.cxx
There are some friendly macros to help you pull out the plots you want in an organized way. Run these guys to output a whole ton of .png files. A few examples are...
> root4star -b -q StRoot/StFgtPool/StFgtClusterTools/macros/saveSignalChar.C'("signalShapes.root")' //this will output histograms per quadrant
> root4star -b -q StRoot/StFgtPool/StFgtClusterTools/macros/saveSignalCharAPV.C'("signalShapes.root")' //this will output histograms per APV
> root4star -b -q StRoot/StFgtPool/StFgtClusterTools/macros/saveClusterSizes.C'("signalShapes.root")' //this will output cluster size histograms per quadrant
For now it's been most convenient to just dump the .png files into your protected directory but hopefully something a little more elegant is on its way very soon...

Streamlining the process
Right now we have a shell script that pulls daq files name from a list and then runs over them one after the other, dumping the output .root files into a directory. Look around for things like "runChain.sh" and "l13173068.list" if you want to have a go at that.
> ./runChain.sh > & output.txt
Coming soon: pre-written xml job for STAR scheduler.

Available data sets
Most recent runs are located in http://www.star.bnl.gov/protected/spin/ezarndt/fgt/
Coming soon: plots better organized into a scroll-friendly format.

Online Software

The online software uses the 'JPlot' framework:

 

> cvs co OnlTools/Jevp

> cvs co OnlTools/PDFUtil

> cvs co StRoot/RTS

> cvs co StRoot/StDaqLib

>cvs co StRoot/StEvent

The framework currently only compiles correctly with the 'pro' library version:

> starver pro

> cons

 

To run do:

> OnlTools/Jevp/launch fgtBuilder -file filename -pdf outputfilename.pdf

Jevp instructions can be found in

OnlTools/Jevp/readme.txt

The fgt specific code is in OnlTools/Jevp/StJevpBuilders/fgtBuilder.{h,cxx}

 

 

 

 

 

 

Organization