Problem 1115 - G4eBremsstrahlung (eBrem) gives different results depending on the order of definition of the elements in a material
Summary: G4eBremsstrahlung (eBrem) gives different results depending on the order of ...
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: physics_lists (show other problems)
Version: 9.3
Hardware: Other Linux
: P5 normal
Assignee: Vladimir.Ivantchenko
URL:
Depends on:
Blocks:
 
Reported: 2010-04-23 18:10 CEST by silvia
Modified: 2010-04-29 17:56 CEST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description silvia 2010-04-23 18:10:14 CEST
In the evaluation of the containment efficiency for DBD0nu events in TeO2
crystals I defined the material both as TeO2 and O2Te.
I used PhysicsList.cc of examples/extended/electromagnetic/TestEM9 and I have switched between G4EmStandard, G4EmLivermore, G4EmPenelope and PhysListEmStandard. 

The results I obtain are:


PhysListEMStandard  TeO2 87.76 +/- 0.13 %
                    O2Te 86.14 +/- 0.13 %
G4EmStandard        TeO2 87.76 +/- 0.13 %
                    O2Te 86.21 +/- 0.13 %
G4Livermore         TeO2 88.49 +/- 0.13 %
                    O2Te 88.46 +/- 0.13 %
G4Penelope          TeO2 88.77 +/- 0.13 %
                    O2Te 88.85 +/- 0.13 %

The efficiencies obtained with PhysListEMStandard and G4EmStandard change depending on the order of definition of the elements in the material but if I substitute in PhysListEMStandard the eBrem model (used below 1 GeV) with LowEnBrem (below 1 GeV) I obtain results compatible with G4Livermore:
                    TeO2 88.45 +/- 0.13 %
                    O2Te 88.42 +/- 0.13 % 
so the problem seems to be in the eBrem model.
Comment 1 Vladimir.Ivantchenko 2010-04-26 17:43:35 CEST
Hello,

Thanks for the report,
Please, send tar file with your application. If you are using TestEm9, please, inform what version of G4 and send your macro-file.

Vladimir
Comment 2 Vladimir.Ivantchenko 2010-04-29 17:56:30 CEST
Hello,

The problem is fixed. The fix will be available in the next public version of Geant4 (June 2010).

VI