Tags:
, view all tags
-- BrendanKiburg - 15 Jan 2008

The following are some of the tasks that should be in place before starting the mini production pass in the next week or so Analysis information

  1. CVS should be kept up to date so developers can properly integrate their code DONE
  2. FADC analysis integrated into the production code DONE
  3. Neutron analysis integrated into the production code
  4. WFD analysis integrated into the production code
  5. Discussion about what data, if any, should be skimmed from these files [This only needs to be done once]
  6. My changes with respect to : entrance counters, MuStop defintion
Organizational information
  1. CVS should be kept up to date so developers can properly integrate their code
  2. Project space needs to be allocated from NCSA
  3. ODB files and Parameters file need to be used separately for run 10, run 11 files
  4. A run list needs to be selected (neutron, muminus, muplus, run10, run11)
  5. The files need to be transferred to scratch or project space prior to launching the jobs.

Proposed plan

  1. "Complete" the steps in "Analysis Information," and run over a few files
  2. Individual users check that relevant histograms/data appear in the root/tree files and match the output from their code
  3. When those are signed off on, we can run over several hundred files with 'mu'
  4. Those can be processed with mta
  5. Results can be summed and examined
Edit | Attach | Watch | Print version | History: r14 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2008-01-15 - BrendanKiburg
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback