TopNtuples From 5.3.1 Production Output

Prescription

    # Create test release
    setup cdfsoft2 5.3.1
    newrel -t 5.3.1 topnt_531
    cd topnt_531

    # Get TopMods with CosmicFinder patch installed
    addpkg TopMods top_5_3_1_v01
    # Get patches
    cvs co Release
    cvs co -A cdfopr
    cdfopr/scripts/checkout_patches 5.3.1_physics

    gmake nobin TopMods.bin


    

• TofAlgs : pick up the right TOF calibrations.
• TrackingSi : fix memory leak in beginRun in SiExpected.
• BTagMods : double check if no SvxBeam in SecVtxModule::event.
• UtilMods : put the database sniper back in jail.

CAVEAT!!! If you want to use the UtilMods patch, you have to compile without shared libaries:

    unsetenv USESHLIBS
    gmake nobin TopMods.bin
    

Ntuple files

• Description of files:
  1. BTag : require 1 loose jet only, for b-tagging studies.
  2. Inclusive : No filter requirement. Pass through initial dataset with new objects.
  3. Lepton : Tight lepton cuts, minus isolation requirement.
  4. W : Tight lepton, plus missing Et.
  5. Z-loose : Tight lepton + loose lepton.
  6. Z-tight : Tight lepton + tight lepton.
• Files are named as:

  topnt_(selection)_gen5val_fixed_(sample)_(sectionnumber).root
  	

  • selection : one of the 6 categories above
  • sample : gjt20d, bhel0d, bhmu0d
  • sectionnumber : CAF section number
• Please note that "missing" files in the "control samples" for btagging are due to the fact that they do not have silicon in any run in that file.
• Location of Data
  • Inclusive Electrons :

    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhel0d/topnt_Inclusive_gen5val_bhel0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhel0d/topnt_Lepton_gen5val_bhel0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhel0d/topnt_W_gen5val_bhel0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhel0d/topnt_Z-loose_gen5val_bhel0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhel0d/topnt_Z-tight_gen5val_bhel0d_*.root
    	    

  • Inclusive Muons :

    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_Inclusive_gen5val_bhmu0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_Lepton_gen5val_bhmu0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_W_gen5val_bhmu0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_Z-loose_gen5val_bhmu0d_*.root
    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_Z-tight_gen5val_bhmu0d_*.root
    	    

  • JET50 :

    fcdfdata047.fnal.gov//cdf/scratch/top/scratch/results/topnt/bhmu0d/topnt_BTag_gen5val_gjt20d_*.root
    	    

  • Sum ET: (from G. Cortiana)

    fcdfdata013.fnal.gov//cdfdata/sumet/gset0d/topntu/topntu531_gset0d_*.root
    	    

CAF Tarballs

• In general:

      % mkdir temp
      % cp submit_top_531.tgz temp/
      % cd temp
      % tar -zxvf submit_top_531.tgz
      % ls
      cafsubmit.csh*  top_531.tgz  submit_top_531.tgz
      % ./cafsubmit.csh
      Usage:  < tarfile > < dataset > < description > [< test=false > < first_sec > < last_sec > < output_location=icaf:temp.tgz >]
  
  	

  Description of input parameters:
  • tarfile : top_531.tgz
  • datset : gjt20d, bhel0d, bhmu0d
  • description : whatever appropriate description you want
  • test : run a test job or not
  • first_sec : first section to submit
  • last_sec : last section to submit
  • output_location : location of tarball.
• The data is split into N sections, where N is the number of filesets.
• PLEASE NOTE! This does not mean there is one fileset per section. The CAF splits by FILE, not by FILESET, so that statement is only ROUGHLY correct.
• To run a test job on the inclusive muons (100 events, 2 sections):

          % ./cafsubmit.csh top_531.tgz bhmu0d gen5val true
          CFSOFT2_DIR :  /home/cdfsoft/dist/releases/development
          Setting default tarfile output location
          Testing only
          Setting to test queue
          Processing:
          Cafcom top_531.tgz icaf:bhmu0d_gen5val_$.tgz rappocc@fnal.gov test 1 2 ./run_topeventmodule.caf $ 1 46 bhmu0d filecatalog false muon gen5val 100
  
          Analysis Farm: caf    Host: fcdfhead1.fnal.gov
  
          JID: XXXXX
  	

• To run the full muon dataset (assuming you have untarred everything, tested it, and it works) :

          % ./cafsubmit_su.csh top_531.tgz bhmu0d gen5val
          CFSOFT2_DIR :  /home/cdfsoft/dist/releases/development
          Setting default tarfile output location
          Processing all events
          Processing all filesets
          Processing:
          Cafcom top_531.tgz icaf:bhmu0d_gen5val_$.tgz rappocc@fnal.gov topstrip 1 46 ./run_topeventmodule.caf $ 1 46 bhmu0d filecatalog false muon gen5val 0
  
          Analysis Farm: caf    Host: fcdfhead1.fnal.gov
  
          JID: XXXXX
  	

Making your own TopNtuples

• To run over a new dataset in DCACHE: Simply edit cafsubmit.csh to be able to handle your new dataset. I usually give the number of sections to be the number of filesets. See the gjt20d entry in cafsubmit.csh for an example.
• To change an existing dataset in ROOTD:

  cat rootd_files_topmc_matched.txt
  root://fcdfdata031.fnal.gov//cdf/scratch/cdfmc/from_toronto/531_with_MC_matching/ttbar_531.*.root
  
  Change this file to whatever you want:
  --------------------------------------
  
  cat "wherever your tarfiles are" > rootd_files_my_new_mc.txt
  tar -chvzf my-favorite-directory/my_new_tarfile.tgz *
  
  Then, you can run using the cafsubmit.csh command:
  --------------------------------------------------
  
  ./cafsubmit.csh my-favorite-directory/my_new_tarfile.tgz ttbar_matched my_description
  

• To add a new dataset in ROOTD, you need to follow the instructions for changing an existing datest, and then modify cafsubmit.csh to handle it. See cafsubmit.csh for ttbar_matched for an example.