Chris, maybe it should have been made more more explicit to users are
large that this superseeds calls such as
root scaler.c
root flr.C
root flrpm.C
where scaler.c, flr.c, flprm.c where snippets of code to set the "proper"
ntuple name in init.C. Standard ntuples and filtered ntuples (lr, flr,
scaler) are still generated in $ANALDIR.
Or am I absolutely wrong ? .....
-- t
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Fri, 19 Mar 2004, Chris Crawford wrote:
> hi,
> i changed init.C so you can specify the path to your ntuples, and the
> ntuple name on the command-line. so you can easily substitute your own
> filtered ntuple into any analysis macro. here is the log message:
>
>
> new method for specifying ntuple and directory:
> 'root init.C path/NTUPLE -o output/path/NTUPLE 3000-3100
> -d new/path/and/NTUPLE 3100-3200'
>
> where NTUPLE is the name of the ntuple,
> and the path can be absolute, or relative to:
> $ANALDIR (*/*), $PWD (./*) (../*) , $HOME (~/*)
>
> example:
> root v3_1/lr 3000-4000 //lr ntuple in $ANALDIR/v3_1
> [root] filter("ntl<8","myflr"); //filters to myflr in $ANALDIR/v3_1
> [root] init("myflr") //start using filtered ntuple
> [root] myflr->Draw("...")
> [root] lr->Draw("") //old ntuple still there, just not default
> [root] init() //reset to lr ntuple
>
> --chris
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST