sPHENIX MAPS tracker discussion

[Ming Liu <ming AT bnl.gov>]

Hi Martin,

Thanks for your comments and the links to documents. 
These examples are meant for training newbies on sPHENIX/MVTX, not really for 
checking the long run data. 
Probably we should update the note just showing more commonly used commands..

Cheers,
Ming 
 
PS - thanks for your help setting up data transfer to RCF, we successfully 
transferred a few samples to RCF today, the real test will come tomorrow!


-- 
Ming Xiong Liu
P-25, MS H846                     TEL: 505-667-7125 
Physics Division                            631-344-7821(BNL)
LANL                                               630-840-5708(FNAL)
Los Alamos, NM 87545      FAX:  505-665-7020
 

On 5/19/19, 10:32 PM, "sPHENIX-MAPS-l on behalf of Martin Purschke" 
<sphenix-maps-l-bounces AT lists.bnl.gov on behalf of purschke AT bnl.gov> wrote:

    Hi Ming, all,
    
    nice summary.
    
    Just out of curiosity, I'm wondering why, under the "cheatsheet felix
    rcdaq", so much emphasis is placed on getting at the last event?
    
    > get last event number:
    > dlist ../beamtest2018/calib/calib_00000708-0000.prdf -n 0 -i |tail
    > 
    > display last event (use last event number from above command):
    > ddump ../beamtest2018/calib/calib_00000708-0000.prdf -n 10 -e 47892 
-g|less
    > 
    > count events:
    > dlist ../beamtest2018/calib/calib_00000708-0000.prdf -n 0|wc
    > 
    
    There is hardly a situation I could imagine where this is a required, or
    even useful, information that rcdaq doesn't give you already? I mean,
    all of those are *really* expensive commands, as you are parsing the
    entire file just to get at a number.
    
    I'm triggering on those kind of things because an early PHENIX
    production manager repeatedly brought the RCF down to its knees by doing
    something along those lines - he didn't know better and thought that the
    processing macro would need the number of events up front.
    
    BTW, the easiest and cheapest (but still expensive) way is
    
     dpipe -s f -d n -i file_name | wc -l
    
    (that also counts special events). You "pipe" the events from a file (-s
    f) to "nowhere" ( -d n), identifying each event as you go (-i), and then
    count lines. No decoding, although you still read the entire file.
    
    Some deeper info at
    
    
https://www.phenix.bnl.gov/~phoncs/oncs/code_documentation/Event/index.html
    
    and
    
    
https://www.phenix.bnl.gov/~phoncs/oncs/code_documentation/Event/dlistddumpanddpipe.html
    
    Best,
        Martin
    
    
    On 5/19/19 19:41, Ming Liu wrote:
    > Hi all,
    > 
    >  
    > 
    > Here is the web site for MVTX test beam activity website,
    > 
    > https://p25ext.lanl.gov/maps/beamtest_2019/index.html
    > 
    >  
    > 
    > Beam is expected tomorrow morning 8:00AM, and we are ready.  
    > 
    >  
    > 
    > Cheers,
    > 
    > Ming 
    > 
    > 
    > _______________________________________________
    > sPHENIX-MAPS-l mailing list
    > sPHENIX-MAPS-l AT lists.bnl.gov
    > https://lists.bnl.gov/mailman/listinfo/sphenix-maps-l
    > 
    
    
    -- 
    Martin L. Purschke, Ph.D.        ;   purschke AT bnl.gov
                                     ;   http://www.phenix.bnl.gov/~purschke
                                     ;
    Brookhaven National Laboratory   ;   phone: +1-631-344-5244
    Physics Department Bldg 510 C    ;   fax:   +1-631-344-3253
    Upton, NY 11973-5000             ;   skype: mpurschke
    -----------------------------------------------------------------------
    _______________________________________________
    sPHENIX-MAPS-l mailing list
    sPHENIX-MAPS-l AT lists.bnl.gov
    https://lists.bnl.gov/mailman/listinfo/sphenix-maps-l