It seems there are differences in the EM option setup when one uses an EM option globally, like e.g. with _EMZ physics lists vs. assigning G4EmStandard_opt4 to one region. Although this test was done with Geant4 10.4.p02, the 10.5 version seems to exhibit a similar behavior. Excerpts from log files are provided below. Problematic lines are marked with <----- -=-=-=-=- ************************************************************** Geant4 version Name: geant4-10-04-patch-02 (25-May-2018) Copyright : Geant4 Collaboration References : NIM A 506 (2003), 250-303 : IEEE-TNS 53 (2006), 270-278 : NIM A 835 (2016), 186-225 WWW : http://geant4.org/ ************************************************************** ... G4PhysListFactory::GetReferencePhysList <QGSP_BERT> EMoption= 0 <<< Geant4 Physics List simulation engine: QGSP_BERT 4.0 <<< Reference Physics List QGSP_BERT is built Assigning G4EmStandard_opt4 to the tracker ... ### === Deexcitation model UAtomDeexcitation is activated for 2 regions: <----- should be 1 DefaultRegionForTheWorld 0 0 0 Tracker 1 0 0 ... msc: for e+ SubType= 10 RangeFactor= 0.04, stepLimitType: 1, latDisplacement: 1 <------ Different RangeFactor? ===== EM models for the G4Region DefaultRegionForTheWorld ====== UrbanMsc : Emin= 0 eV Emax= 100 MeV Table with 42 bins Emin= 100 eV Emax= 100 MeV WentzelVIUni : Emin= 100 MeV Emax= 100 TeV Table with 42 bins Emin= 100 MeV Emax= 100 TeV ===== EM models for the G4Region Tracker ====== GoudsmitSaunderson : Emin= 0 eV Emax= 100 MeV Table with 42 bins Emin= 100 eV Emax= 100 MeV <----- Different number of bins? WentzelVIUni : Emin= 100 MeV Emax= 100 TeV Table with 42 bins Emin= 100 MeV Emax= 100 TeV eIoni: for e+ SubType= 2 dE/dx and range tables from 100 eV to 100 TeV in 84 bins Lambda tables from threshold to 100 TeV, 7 bins per decade, spline: 1 finalRange(mm)= 0.01, dRoverRange= 0.2, integral: 1, fluct: 1, linLossLimit= 0.01 ===== EM models for the G4Region DefaultRegionForTheWorld ====== <----- No other region mentioned ? MollerBhabha : Emin= 0 eV Emax= 100 TeV vs. G4PhysListFactory::GetReferencePhysList <QGSP_BERT_EMZ> EMoption= 4 <<< Geant4 Physics List simulation engine: QGSP_BERT 4.0 <<< Reference Physics List QGSP_BERT_EMZ is built ... msc: for e+ SubType= 10 RangeFactor= 0.2, stepLimitType: 2, latDisplacement: 1 ===== EM models for the G4Region DefaultRegionForTheWorld ====== GoudsmitSaunderson : Emin= 0 eV Emax= 100 MeV Table with 120 bins Emin= 100 eV Emax= 100 MeV WentzelVIUni : Emin= 100 MeV Emax= 10 TeV Table with 100 bins Emin= 100 MeV Emax= 10 TeV eIoni: for e+ SubType= 2 dE/dx and range tables from 100 eV to 10 TeV in 220 bins <------ Lambda tables from threshold to 10 TeV, 20 bins per decade, spline: 1 finalRange(mm)= 0.01, dRoverRange= 0.2, integral: 1, fluct: 1, linLossLimit= 0.01 ===== EM models for the G4Region DefaultRegionForTheWorld ====== PenIoni : Emin= 0 eV Emax= 1 MeV MollerBhabha : Emin= 1 MeV Emax= 10 TeV deltaVI
Hello Krzysztof, Thanks for this report. Some improvements are added to the development version. After validation it may be part of the patch. The fix was tested with TestEm8 and macro file attached to this report. Vladimir
Created attachment 548 [details] macro file for TestEm8
Hi Krzysztof, is it possible to check the issue with 10.6? Cheers, Vladimir
Hi Vladimir, Thanks for working on it. It does look better, however, I still see at least one difference. Namely, note the RangeFactor & stepLimType below in msc. Krzysztof QGSP_BERT + EmStandardPhysics_option4 in TrackerMother msc: for e- SubType= 10 RangeFactor= 0.04, stepLimType: 1, latDisp: 1 ===== EM models for the G4Region DefaultRegionForTheWorld ====== UrbanMsc : Emin= 0 eV Emax= 100 MeV Nbins=120 100 eV - 100 MeV WentzelVIUni : Emin= 100 MeV Emax= 100 TeV Nbins=120 100 MeV - 100 TeV ===== EM models for the G4Region TrackerMother ====== GoudsmitSaunderson : Emin= 0 eV Emax= 100 MeV Nbins=120 100 eV - 100 MeV WentzelVIUni : Emin= 100 MeV Emax= 100 TeV Nbins=120 100 MeV - 100 TeV vs. QGSP_BERT_EMZ msc: for e- SubType= 10 RangeFactor= 0.08, stepLimType: 2, latDisp: 1 ===== EM models for the G4Region DefaultRegionForTheWorld ====== GoudsmitSaunderson : Emin= 0 eV Emax= 100 MeV Nbins=120 100 eV - 100 MeV WentzelVIUni : Emin= 100 MeV Emax= 100 TeV Nbins=120 100 MeV - 100 TeV
Hi Krzysztof, it seems, that your recent concern is researved in ref-01 and in the patch to 10.6. Please, confirm. Vladimir
Hi Vladimir, May be it is just the printout, but I do not see any difference between 10.6 and 10.6.p01 for msc. Also, may be I missed it previously, but should conv not have have it's own region printout as well? QGSP_BERT + EmStandardPhysics_option4 in TrackerMother conv: for gamma SubType=14 BuildTable=1 Lambda table from 1.022 MeV to 100 TeV, 20 bins/decade, spline: 1 ===== EM models for the G4Region DefaultRegionForTheWorld ====== BetheHeitlerLPM : Emin= 0 eV Emax= 100 TeV ModifiedTsai vs. QGSP_BERT_EMZ conv: for gamma SubType=14 BuildTable=1 Lambda table from 1.022 MeV to 100 TeV, 20 bins/decade, spline: 1 ===== EM models for the G4Region DefaultRegionForTheWorld ====== BetheHeitler5D : Emin= 0 eV Emax= 100 TeV ModifiedTsai Could you also double check eIoni, eBrem, ePairProd, ionIoni, nuclearStopping, hIoni, muIoni (and probably others) which printout does not seem right? Krzysztof
Hi Krzysztof, it seems that I did max for 10.6ref07 in this area. Note, that enabling of different EM option for a region cannot be fully equivalent to the case, when this extra option is defined for all setup, because not all EM options defined per region, some are global. At least, with this version it seems, that the printout at initialization is correct. I plan to close this ticket. Cheers, Vladimir
