Ignore:
Timestamp:
11/05/11 10:53:07 (13 years ago)
Author:
neise
Message:
initial commit of flightpulser.C with an additional method in zerosearch.C and an entry in README.txt
Location:
fact/tools/rootmacros
Files:
1 added
3 edited

Legend:

Unmodified
Added
Removed
  • fact/tools/rootmacros/README.txt

    r12389 r12391  
    3232        root -l -q fbsl.C++'("/data00/fact-construction/raw/2011/10/26/20111026_036.fits.gz", "/data00/fact-construction/raw/2011/10/26/20111026_031.drs.fits.gz", "./fbsl.txt", "./20111026_036.root")'
    3333
    34 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    3534
     35-----------------------------------------------------------------------------------------------
    3636fpeak_cfd.C             ROOT macro creating an amplitude spektrum for each pixel
    3737
     
    6363
    6464
    65 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
     65-----------------------------------------------------------------------------------------------
    6666
    6767gainfit.C ROOT macro for analysing the amplitude spektra of fpeak_cfd.C
     
    8181
    8282
     83-----------------------------------------------------------------------------------------------
     84flightpulser.C ROOT macro for plotting the amplitudes of the external lightpulser
     85
     86call it e.g. like this
     87root
     88flightpulser.C+'("data/20111029_017.fits.gz","data/20111029_013.drs.fits.gz","../analysis/20111029_017-013_fpeak_cfd.root",
     890, 100, 0,-1)'
     90
     91to look at the amplitudes of all camera pixel for 100 events.
     92you get a color coded TH2F so you can look at the amplitude distribution
     93yourself.
     94
     95this macro is based on fpeak_cdf.C pretty much.
     96I basically use the same steps, but in the end I just fill the absolute
     97maximum into the TH2F.
     98
     99The macro is pretty slow (about 1.5 min for 100 full camera events) so I
     100switched off the sliding averages...
     101
     102but it didn't help much...
     103
     104I am still not sure how to improve the speed of these macros.....
     105
     106
  • fact/tools/rootmacros/zerosearch.C

    r12382 r12391  
    349349}
    350350
     351Region FindAbsMax(
     352        vector<Region> &regions,
     353        int VerbosityLevel)
     354{
     355        Region AbsMax;
     356        AbsMax.begin = -1;
     357        AbsMax.maxPos = -1;
     358        AbsMax.end = -1;
     359        AbsMax.maxVal=-numeric_limits<float>::max();
     360        if (regions.size() < 1)
     361                return AbsMax;
     362
     363        for (vector<Region>::iterator it = regions.begin(); it < regions.end(); ++it)
     364        {
     365                if (it->maxVal > AbsMax.maxVal ) {
     366                        AbsMax = *it;
     367                }
     368        }
     369        return AbsMax;
     370}
     371
    351372////////////////
    352373////////////// old Version of the code
  • fact/tools/rootmacros/zerosearch.h

    r12382 r12391  
    5353        int VerbosityLevel=0);
    5454
     55Region FindAbsMax(
     56   vector<Region> &regions,
     57   int VerbosityLevel=0);
     58
    5559#endif
Note: See TracChangeset for help on using the changeset viewer.