Request 25: General-purpose, 50M UrQMD BiBi@9.2 (second collaboration paper)

!!! Test/QA production stage !!!

UrQMD + Geant-4 based general-purpose simulation project for minbias (b = 0-16 fm) Bi (83/209) +Bi (83/209) collisions at 9.2 GeV, full detector configuration.

Please find below the request details:

inputfile (444 Bytes)
MpdDecayConfig.txt (352 Bytes)
g4Config.C (3.0 KB)
MpdStack.cxx (24.1 KB)
MpdTofHitProducer.cxx (9.9 KB)
MpdTofHitProducer.h (2.3 KB)
runMC.C (11.2 KB)
reco.C (8.7 KB)

Configuration:

  1. inputfile - UrQMD input file that simulates minbias (0-16 fm) BiBi@9.2 collisions, sets resonances (rho, phi, K*, Lambda*, Sigma*, Xi*) as stable particles to be later decayed by Geant-4. Important: The value of ‘rsd’ parameter should be set as a unique integer for each UrQMD run.
  2. runMC.C file was modified to use Pythia-8 for resonance decays for realistic mass shapes.
  3. reco.C - full detector reconstruction, including the ECAL.
  4. MpdDecayConfig.txt file was modified to set the PDG branching ratios for e+e- decays of rho, omega, phi.
  5. MpdStack.cxx file was modified to suppress tons of output lines in the log files.
  6. g4Config.C file was modified to increase maximum number of steps in tracking of heavy fragments to reach FHCAL/FFD
  7. MpdTofHitProducer.cxx(h) files were modified to include b-dependent smearing of T0 for TOF

Make a fresh check-out of the -dev branch of the MpdRoot, replace:
detectors/tof/MpdTofHitProducer.cxx
detectors/tof/MpdTofHitProducer.h
simulation/mcStack/MpdStack.cxx
gconfig/MpdDecayConfig.txt
gconfig/g4Config.C
files with the attached versions and then compile.

For simulation, please use the attached runMC.C macro.
For reconstruction please use the attached reco.C macro. It produces standard DST files.

To validate the production configuration, we need ~ 1,000,000 events reconstructed for QA.
The output files will have to be copied and stored at NICA cluster.
The ‘mpdroot’ should be tagged for this production.

QA: /eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp07-22-500ev-req25/BiBi/09.2GeV-mb/urqmd/BiBi-09.2GeV-mp07-22-500ev-req25

Thanks a lot for the QA sample. We are ready to move to full-size production after a few changes:

  1. We updated inputfile for UrQMD. Input files should be reproduced anew and used for this production and for production Request 28 (reduced magnetic field).
  2. Please delete QA sample, it was produced with the previous version of the inputfile.
  3. Please produce 50 M events and copy DST files to NICA cluster.
  4. Please produce an additional 1M events with another inpitfile attached below. This inputfile generates events in a wider range of impact parameter for centrality studies:
    inputfile (444 Bytes)
    The same sample of input files will be used for Request 28 with the reduced magnetic field.
    Copy DST files to NICA cluster, one should be able to separate these files from the others.
  5. Please copy to the NICA cluster one of the files produced after runMC.C macro. it is needed for geometry initialization in some of post-processing macro.
    Thanks!

centrality studies sample:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp07-22-500ev-req25cs/BiBi/09.2GeV-mb/urqmd/BiBi-09.2GeV-mp07-22-500ev-req25/
Output from runMC.C:
/eos/nica/mpd/sim/data/mc/urqmd-BiBi-09.2GeV-mb-eos0-500-0.dst.root

Я посмотрел на выходные файлы и вижу, что прицельный параметр распределен в интервале 0-16 fm:


Хотя для “centrality studies sample” он должен быть распределен в интервале 0-18 fm. Вы не проверите какую версию inputfile вы использовали? Четвертая строчка сверху “imp -18” задает диапазон по прицельному параметру.

Dear colleagues,
I don’t see any dst files for this request anymore neither from ncx nor from hydra machines. Were they removed till reproduction with new impact parameter or something is not working?

These were qa data. After analyzing this data, it was decided to change the generation settings. Because these data now do not correspond to the production configuration, I deleted them.
The set for studying centrality was incorrectly calculated, the data was also deleted, now the main production and recalculation of the set for centrality is running. The data is placed in the main production storage on the tier cluster. When finished, I will copy the data to the NICA cluster. Storage space is not infinite, irrelevant data is deleted, unused data I move to tapes.

Thank you for the clarification Andrej.

production data in the process of copying to:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp07-22-500ev-req25/BiBi/09.2GeV-mb/urqmd/BiBi-09.2GeV-mp07-22-500ev-req25/
centrality studies sample already in:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp07-22-500ev-req25cs/BiBi/09.2GeV-mb/urqmd/BiBi-09.2GeV-mp07-22-500ev-req25/
Output from runMC.C:
/eos/nica/mpd/sim/data/mc/urqmd-BiBi-09.2GeV-mb-eos0-500-0.dst.root

Slides with results from centrality determination procedures (MC-Glauber and inverse Bayes based methods) for this data set are attached here:
QAreq25_ver2.pdf (1.4 MB)

1 Like

Dear Peter,

Thanks for posting the slides. There is a special subproduction of 1M events that is intended for centrality studies with the impact parameter distribution in the range 1-18 fm:
/eos/nica/mpd/sim/data/exp/dst-BiBi-09.2GeV-mp07-22-500ev-req25cs/BiBi/09.2GeV-mb/urqmd/BiBi-09.2GeV-mp07-22-500ev-req25/
Also the presented study leaves aside events with |z-vertex| > 50 cm, which constitute ~ half of the sample. We need to discuss the centrality measurement strategy at the next cross-PWG meetings.