Re: (Br)TrackingEfficiencyFinder

From: Christian Holm Christensen (cholm@hehi03.nbi.dk)
Date: Sun Oct 14 2001 - 10:25:20 EDT

  • Next message: Ramiro Debbe: "Re: Shift report 20011014 00:00-08:00"

    Hi Pawel et al, 
    
    On Fri, 12 Oct 2001 13:44:05 +0200
    Pawel Staszel <staszel@alf.nbi.dk> wrote
    concerning "(Br)TrackingEfficiencyFinder":
    > This package allows to find the track reconstruction efficiency ...
    
    Cool! 
    > Of course, a standard options  like -s -n -H are possible as well.
    
    Uh? I've never seen any standard use of -s and -n. -H useally denotes
    the histogram output file. -n could possible be number of events,
    though I believe the -e option is more widely used for that.  
    
    Anyway, I guess you used the BrAppOptionManager for all this, so there
    should be little problem, since one can simply do --help to get a list
    of options. 
    
    But, and it's a question Flemming has raised before, perhaps we should
    agree on some standard meaning of various options.  That will make
    life easier for all of us.  Here's what I believe is the de facto
    standard, intermingled with my suggestions: 
    
      -h   --help            b  Show help (already in the manager, so standard) 
      -V   --version         b  Show version (already in the manager, so standard) 
    
      -i   --input           s  Single file input name (and not directroies)
      -o   --output          s  Single file output name 
      -H   --histogram       s  Single file histogram output
    
      -I   --input-directory s  Where to find input files 
      -F   --max-files       i  Maximum number of input files (e.g., sequences)
      
      -v   --verbose         i  Verbosity level 
      -d   --debug           i  Debug level 
      
      -m   --magnet		 s  Magnet ASCII file (should go away soon) 
      -g   --geometry        s  Geometry ASCII file (should go away soon) 
    
      -r   --run             i  Run number 
      -e   --max-events      i  Max number of events 
    
      -M   --maindb-host     s  Main Database host 
      -D   --maindb-name     s  Main Database name 
      -U   --maindb-user     s  Main Database user  
    
    [b = boolean, i = integer, s = string, f = float] 
    	
    There may be more options that we would want to standarise, and if you
    can think of some, please answer to this message.  Please remember
    though, that we don't want standarised options for things like 'the
    adc gain in TOF1 slat 5, top tube'. 
    
    Individual user/developers are then free to use the rest of the
    alphabet to define other options.  For example could one think of
    things like 
    
      -z  --max-vertex-z  f   Maximum absolute value of primary vertex Z coord.
      -t  --triggers      s   list of triggers to use. 
    
    At some point, I'd like to make an option that is repeatable, so you
    could do 
    
      ./myapp -t 1 -t 5 -t 6 ...
    
    and then get the list of values like 
    
    
      tOption->GetValue(0); 
      tOption->GetValue(1); 
      tOption->GetValue(2); 
    
    As it is now, any later occurence of the same option, will override
    the former.  In particular, if you have a boolean option, which per
    default is true, and you specify it twice on the commandline, it will
    end up being true again.  
    
    Yours, 
    
    Christian Holm Christensen -------------------------------------------
    Address: Sankt Hansgade 23, 1. th.           Phone:  (+45) 35 35 96 91 
             DK-2200 Copenhagen N                Cell:   (+45) 28 82 16 23
             Denmark                             Office: (+45) 353  25 305 
    Email:   cholm@nbi.dk                        Web:    www.nbi.dk/~cholm
    
      
    



    This archive was generated by hypermail 2b30 : Sun Oct 14 2001 - 10:25:50 EDT