TO FIND RUNS:

From Penny KASPER (thanks!):

The offline run database is at the following URL:

 http://d0db.fnal.gov/run/runQuery.html#

 To find recorded cosmic runs -

 1. Fill in a run range  (eg >251000 , < 252000)
 2. put %cosmic%  for the trigger list name
 3. select recording ON
 4. select solenoid ON
 5. select toroid ON
 6.  Click "run"

Run numbers for cosmic runs:
251972
251971
251540
251265
251237
251116
251012


TO RECONSTRUCT RAW DATA AND MAKE tmb's:

From Herb Greenlee (thanks!):

setup D0RunII p20.12.05c
setup sam

sam translate constraints --dim="RUN_NUMBER 251237"

(sam translate constraints --dim=help       ***to see more options)

sam create dataset definition --defname=cosmic_run251237_120609 \
  --group=dzero --dim="RUN_NUMBER 251237"

setup d0tools
setup D0RunII p20.12.05c
newrel -t p20.12.05c /prj_root/3001/ckm_write/bruce1/BH_reco   ***or you target directory
cd /prj_root/3001/ckm_write/bruce1/BH_reco
d0setwa

(runreco -h            ***to get help)

runreco -format=data -defname=cosmic_run251237_120609 -cabsrv1 -maxopt \
  -scratch=/prj_root/3001/ckm_write/bruce1/scratch  -batch

The tmb's land in the scratch area in this case.


TO CONVERT THE tmb's to AADST'S:

cd /work/naia-clued0/bruce1
setup D0RunII p20.12.05c
newrel -t p20.12.05c make_AADST
cd make_AADST
kinit -f
addpkg d0reco
addpkg -h AATrack
source AATrack/script/setup.csh
6. edit file d0reco/bin/OBJECTS
     - add line: RegUnpThumbNailPkg
gmake
cp AATrack/rcp/runD0reco_ana.rcp d0reco/rcp/
cp AATrack/rcp/runD0recoSAM_ana.rcp d0reco/rcp/
cp AATrack/script/post.csh .
11. Create SAM definitions (did this before)
sam create dataset definition --defname=cosmic_run251237_120609 \
  --group=dzero --dim="RUN_NUMBER 251237"
12. submit jobs to CAB using the following command:
setwa
kinit -f
setup d0tools
setup D0RunII p20.12.05c
d0setwa
    runreco -localfwkrcp -localbuild -localrcp -maxopt \
    -format=ana -userpostscript=post.csh \
    -initscript=initchunkanalyze.sh -sourcescript=chunkanalyzesource.sh \
    -filelist=files -group=dzero -nofpe \
    -cabsrv2 -cabtar=tarball_p20.12.05c_2.tar -jobs=1 \
    -scratch=/prj_root/3001/ckm_write/bruce1/scratch \
    -caboutpath=/work/naia-clued0/bruce1/make_AADST

with

/prj_root/3001/ckm_write/bruce1/scratch/D0reco_x-p20.12.05c-maxopt-Linux-cosmic_run251237_120609-1075822/tmbfile

in "files".


                 Detailed instructions on production of AADST
                  (inclusive muon skim)

0.  setup D0RunII p17.09.03
1.  newrel -t p17.09.03 p17.09.03-prod
2.  cd p17.09.03-prod
3.  addpkg d0reco
4.  addpkg -h AATrack
5.  source AATrack/script/setup.csh
6.  edit file d0reco/bin/OBJECTS
     - add line: RegUnpThumbNailPkg
7.  gmake
8.  cp AATrack/rcp/runD0reco_ana.rcp d0reco/rcp/
9.  cp AATrack/rcp/runD0recoSAM_ana.rcp d0reco/rcp/
10. cp AATrack/script/post.csh .
11. Create SAM definitions
    - suggestion: it is convenient to work with data sets
      containing ~15-20 Mln raw events. The size of data sets
      can be adjusted by changing CREATE_DATE dimension.
    There are 2 types of data sets for p17 processing.
    see: http://www-d0.fnal.gov/Run2Physics/cs/skimming/fixPass2p170903.html
    Your data set definition can look like:

    sam create dataset definition --defname=p17.09.03_06011016 \
    --group=dzero --dim="appl_name p17tmbfixer and version p17.09.03 \
    and data_tier thumbnail and solenoid_current > 4000 \
    and create_date >= 01/10/2006 and create_date < 01/16/2006"

   Notice: For the future arrangement of data it is important that
   you use "underscore" ("_") and not "hyphen" ("-") in the name of
   the data set.

12. submit jobs to CAB using the following command:

    runreco -localfwkrcp -localbuild -localrcp -maxopt \
    -format=ana -userpostscript=post.csh \
    -initscript=initchunkanalyze.sh -sourcescript=chunkanalyzesource.sh \
    -defname=<your data set> -group=dzero -nofpe \
    -cabsrv2 -cabtar=tarball_17.09.03.tar -jobs=30 \
    -scratch=<your scratch area> \
    -caboutpath=<your output area>
    Comments:
     <your data set> - SAM data set
     -jobs=30 - number of jobs. Suggested number is 30
     -cabsrv2 - can be changed to -cabsrv1, depending which server
                is more empty
     <your scratch area> - place where the tarball will be placed.
     <your output area>  - place where output of jobs will be placed
                           Notice: It is suggested to have the output
                           area on the same disk as the future permanent
                           location of AADST. It will be very simple
                           to move files to the permanent location
                           using the script described below
     tarball_17.09.03.tar - name of tarball file which will be created
                            it can be changed to any other name