Hello Tongtong,
I'm seeing output files showing up in recon and rootTree, but nothing in log. Where are the log files being written to?
Norman
On Jul 17, 2019, at 11:09 AM, Tongtong Cao <[log in to unmask]> wrote:
[log in to unmask]"><catagoriesOfRuns2019.xlsx>Dear Colleagues,
According to the run list in Run Spreadsheet 2019, I categorized runs (collected so far) as “Ecal Pedestal”, “SVT OFF” and “SVT ON” after dropping junk runs.A table is attached.
There are two steps for cooking:Step 1: Decoding and reconstruction using the up-to-date “SNAPSHOT-bin.jar"Parameter setup in the current jsub.xml:1) -d (detector): HPS-PhysicsRun2019-v1-4pt52) -x (steering file): PhysicsRun2019_testRecon.lcsim for “SVT ON” runs, and PhysicsRun2019_NoSVT.lcsim for “SVT OFF” runs3) -R (run number): ${run} (run number of processed run)Step 2: Conversion from LCIO file into ROOT file using Make_Root.cc/Make_Root_NoSVT.cc for convenience of C++ users
Other setup in the current jsub.xml:# of processed files for a given run: all files if # < 15, 15 files (5 at first, 5 in the middle, and 5 at the end) if # >= 15Destination of output: /volatile/hallb/hps/data/run2019/ConcurrentCook/${run}; /volatile/hallb/hps/data/run2019/ConcurrentCookfail/${run} (if failed)
To request a run/runs for data cooking, please provide run number(s) and special requests, like # of processed files or a list of processed files for a run, output storage for the long-term usage (the default “volatile" storage temporarily keep output), etc.
So far, runs 9569 (SVT OFF) and 9600 (SVT ON) have been cooked.
ps: Please add notes for each run during shifts.
Best regards,Tongtong