QCD News
Frank Chlebana
April 20, 2001
MC Issues
We've been asked to provide a MC liaison (form a QCD MC subgroup) to help organize the QCD MC requests that will be submitted to the offline farm.

For more details see: http://ncdf76.fnal.gov/qcd/mc/

Rick Field has agreed to represent us. It would be useful to find a second person...

We need to define some standard TCL scripts that can be used to generate some common processes. Make these available to the rest of the group...

Can use the batch system (setup lsf) on fcdfsgi2 to generate test samples of the MC. Should put the files in the QCD area.

Once we are happy with a test job we should try to submit a larger job to be run on the offline farm.

To run different MC generators through the CDF simulation you can use cdfSim. May want to add additional modules so we can start from the cdfSim template and See DataAccess/test/runMC.cc as an example.

For example we may want to have the full chain working in one executable: MC generator -> cdf simulation -> trigger simulation -> QCD ntuple maker.

Was able to run herwig in 3.13.0 but have problems running in newer releases.
Some tasks for the QCD MC subgroup:
  • Come up with generator settings to be used for some typical processes.
  • Work with simulation people to make sure we are using the correct version and have the simulation configured properly.
  • Set up the MC executable.
  • Sort out request within the QCD group for large MC jobs.
  • Make sure that the jobs get processed.
1x8 data is available: A collection of links can be found at: http://ncdf76.fnal.gov/qcd/DataAccess/
  • Gives a list of good runs taken during the 1x8 store.
  • Links to the status of the reconstruction of the runs.
  • Links to examples of how to access the data.
Still need to develop a QCD ntuple. Started to use the ntuple maker in the DataAccess package to write out a few runs in the QCD area on fcdfsgi2: fcdfsgi2:/cdf/data03/s0/qcd/data1
Need someone to take responsibility for defining the QCD ntuple and producing the ntuples.

Two possibilities exist, use the standard ntuple or develop a QCD specific ntuple.

Need to have more people involved in looking at the data and to provide feedback to the detector and reconstruction groups about the quality of the data.

It is also essential to develop the tools to look at the quality of the QCD triggers.

Data can be used to estimate trigger rates...
Jet Corrections: Started to collect information about jet corrections. http://ncdf76.fnal.gov/qcd/runIIPrep/jetCorrections.html This will be one of our major contributions and we need to get started on this now.
Upcoming Collaboration Meeting: We are expected to report on our progress and we should set some goals that we want to accomplish for the meeting.

Analysis Plans
  • Input to PDFs:
    • How to expand our jet measurements to high and low x.
    • Information about the gluon density.
    • W asymmetry u/d ratio
    • Direct photon
    • Give an overview of how these measurement provide complimentary information.
  • QCD triggers: We should make it clear which QCD triggers we are responsible for, have them documented and tested at L3. It would be good to have a note out justifying and documenting the triggers
  • Data quality: We need to have in place some jobs that monitor the quality of the QCD triggers.
  • Progress on jet corrections: Clearly outline a plan and report on our progress
  • QCD ntuple: Standardize the QCD ntuple. Write out ntuples for the data/mc to a common area.
  • MC: Sort out settings for some typical processe. Put together a MC executable. Push some jobs through the offline farm. Make some data sets available in QCD areas on fcdfsgi2.
  • Distributions from Run II data: We should show some "interesting" distributions/events.
Frank Chlebana - April 20, 2001