Request11: PWG4 - dielectrons, 15M minbias BiBi@9.2, new dE/dx

This is a Geant-4 based PWG4 request for a new Monte Carlo production. The production is for Bi (83/209) +Bi (83/209) collisions at 9.2 GeV, which is considered as a day-1 configuration. Extra variables are added to the DSTs to apply dphi/dzed differential matching cuts in the TOF.

Please find below the request details:

inputfile (306 Bytes)
runMC.C (10.2 KB)
reco.C (8.4 KB)
MpdDecayConfig.txt (357 Bytes)
MpdStack.cxx (20.9 KB)
MpdTofMatchingData.cxx (2.8 KB)
MpdTofMatchingData.h (3.4 KB)

This is a general-purpose project, which includes simulation of the MPD-ECAL (v.3 geometry) and has enhanced (x20) probabilities for light vector meson decays to ee+X channels. Since original branching for such decays is 10^-4-10^-5, the enhancement does not affect the simulation of hadrons. Decays of short-lived resonances (to have realistic peak widths) and pi0/eta-meson are managed by Pythia8.

The simulation project consists of a few stages:

  1. Events are generated by UrQMD. It should be run with an attached inputfile, which was set up to generate 500 minbias BiBi@9.2 collisions. Some of the particles are requested to be stable in the input file to be further decayed in the mpdroot.
    Important : The value of ‘rsd’ parameter should be set as a unique integer for each UrQMD run.
  2. Make a fresh check-out of the -dev branch of the MpdRoot, replace
  • mcstack/MpdStack.cxx
  • tof/MpdTofMatchingData.h
  • tof/MpdTofMatchingData.cxx
    files with the attached versions and then compile.
  1. Replace file gconfig/MpdDecayConfig.txt with the attached one.
  2. For simulation, please use the attached runMC.C macro.
  3. For reconstruction please use the attached reco.C macro. It produces standard DST files.

Notes:

  1. In this production, we do not need to store any intermediate files, we need only the DSTs.
  2. To validate the production configuration, we need ~ 200,000 events reconstructed for QA.
  3. The output files will have to be copied and stored at NICA cluster.
  4. The ‘mpdroot’ should be tagged for this production.

QA sample 200 000 events:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp02-21-500ev/BiBi/09.2GeV-mb/UrQMD/BiBi-09.2GeV-mp02-21-500ev
500 events per file

Thanks a lot for the test files. Unfortunately, we see some issues with the production. We need some time to work out the solution.

Dear Andrey, after some studies, we decided to modify the original request. The request details have been updated in the header of the thread. The main changes are that:

  • we move back to the -dev branch of the MpdRoot for the production
  • we increased number of events to 15M

Please remove the produced test files. We are going to need another test run for 200,000 events.

New QA sample at same place:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp02-21-500ev/BiBi/09.2GeV-mb/UrQMD/BiBi-09.2GeV-mp02-21-500ev

Dear Andrey, the test files are fine. Please proceed with the full-size simulation. Thanks.

Fine. The production has been started.

The production is finished. All 30,000 files with 500 events per file are in /eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp02-21-500ev/BiBi/09.2GeV-mb/UrQMD/BiBi-09.2GeV-mp02-21-500ev. The production took 3 days longer than expected due to minor problems on 2 clusters. The production tasks were the most difficult of all 11 productions. Up to 14 hours only for the simulation of 500 events. Many thanks to the LIT team for the additional 520 cores. Regarding the data transmission channel eos-eos VBLHEP-LIT: new switches of 40 gigabits have already been purchased, but have not yet been configured, this will take some time.

Thanks a lot, Andrey!

Dear Andrey,
Are MiniDST files available for this production?

The miniDST production was not requested for the production. They can be produced though.

There was no notification of a new post in the topic. I just read it. MiniDST’s was not in the request, but they can be made.Do it?

Dear Andrei,

I understand it could be done relatively quickly. I think we should do it, and make it standard to produce MiniDST files.

Dear, Adam.
OK.
In future productions, I will always activate the minidst recording. I will start generating minidst for this production soon.