Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Uopdated the log-book table with singMup and singMum .root files and also cleaned up the page

...

ProcessVertexEventsFilename(s)Notes                      
Drell-Yan (DY)




Target300K, 100K, 250KDY_target_300K,   DY_target_100K, DY_target_250K
Dump


Air Gap


No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







JpsiTarget300K, 70K, 130KJPsi_target_300K,  JPsi_target_70K,  Jpsi_target_130K
Dump130KJPsi_Dump_130k
Air Gap


No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







Di-MuonTarget100KDimuon_target_100K
Dump


Air Gap2.5MDimuon_x15y15z300_2.5Mx=15, y=15, z=300
No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







Single-Muon



Target


Dump


Air Gap


No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







Single-Muon plus




Target


Dump


Air Gap370KsingMup_x2y2z300_370K.root
No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







Single-Muon minus





Target


Dump


Air Gap350KsingMum_x2y2z300_350K.root
No Target


All (proper target dimensions)


Just Target (proper target dimensions)


All except Target







...

  • (Example) Differences between event vertex, target and dump.
  • (Example) Difference between truth quantity and reconstructed quantity.

--------------------------------------------------------- The section below will be removed if the above content looks organized ---------------------------------------------------------

  1. Image Removed

Unsorted Info

Kenichi and anyone write down some possibly-useful info here (rather than e-mail).  The info may be moved to a proper section when made use of.

    When you generate single-muon events, you have to change the condition of `SQGeomAcc` in `Fun4Sim.C`.
  • SQGeomAcc skips (i.e. not save) an event in which a muon or a muon pair doesn't pass through the spectrometer acceptance, because such event is useless for analysis.
  • By default, SQGeomAcc requires a muon pair per event; "geom_acc->SetMuonMode(SQGeomAcc::PAIR);"
  • When you generate single-muon events, you have to modify `Fun4Sim.C` as follows, so that SQGeomAcc requires a muon per event;

    geom_acc->SetMuonMode(SQGeomAcc::SINGLE);

      or

    geom_acc->SetMuonMode(nmu_plus+nmu_minus==1 ? SQGeomAcc::SINGLE : SQGeomAcc::PAIR);

    Better configurations for J/psi and psi' are available in the E1039-Collaboration/e1039-analysis repository.  Zulkaida could make use of them in "/project/ptgroup/Akbar/*/Fun4Sim.C".https://github.com/E1039-Collaboration/e1039-analysis/blob/master/SimChainDev/phpythia8_Jpsi.cfg ... It produces J/psi and other charmonia (including psi'), where the rate of psi' is much lower than the current configuration
  • .
  • https://github.com/E1039-Collaboration/e1039-analysis/blob/master/SimChainDev/phpythia8_psip.cfg ... It produces only psi', not J/psi.
  • Note:  Even when using new configurations, you should still select the particle of your interest (i.e. J/psi or psi') by its truth mass in `histo.C`.  It is because a random pair (like mu+ from pi+ and mu- from pi-) could be produced from the beam remnant.
  • reco_vz
    • reco_vz is the reconstructed position of track (not dimuon) at the target position (i.e. z = -300 cm). Therefore "reco_vz" is always -300 cm
    • The meaning of "reco_vz" is defined in "AnaTrkQA".  Actually the present naming is misleading.
    • When dimuon events are produced in the dump, each track should make the closest approach to the z-axis in the dump region. But "reco_vz" is not the position of the closest approach but the position of the track at z = -300 cm by definition.  "reco_vx" and "reco_vy" are not peaked at 0 cm.
  • Others??