Problem 961 - Missing X-ray fluorescence lines?
Summary: Missing X-ray fluorescence lines?
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/electromagnetic/lowenergy (show other problems)
Version: 9.0
Hardware: All All
: P5 trivial
Assignee: alfonso.mantero
URL:
Depends on:
Blocks:
 
Reported: 2007-08-01 19:42 CEST by ahoover
Modified: 2007-08-28 19:45 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description ahoover 2007-08-01 19:42:52 CEST
I am having some difficulty with X-ray fluorescence. I have a very simple test setup: throwing 100 keV photons at a piece of Tin. I record the energy deposit in the Tin, and I expect to see X-ray escape peaks at energies corresponding to 100 keV minus the fluorescent X-ray energies for Tin. The problem is that the code does not seem to be generating the X-ray corresponding to the first line of data in the G4EMLOW4.3/fluor/fl-tr-pr-50.dat file. The first few lines of the file look like this:

1            1            1            
5            0.248181     0.0250232    
6            0.464342     0.0252572    
10           0.0418921    0.0284306    
11           0.0813413    0.0284737
...


I see an escape peak corresponding to the 25.2572 keV X-ray, but not for the 25.0232 X-ray. This same behavior has been verified for other elements. If I add a dummy line to the file like this:

1            1            1   
0            0            0         
5            0.248181     0.0250232    
6            0.464342     0.0252572    
10           0.0418921    0.0284306    
11           0.0813413    0.0284737
...

then both X-ray escape peaks appear as I would expect. So, it seems the code is not reading or not using the first line of data in the data files.
Comment 1 Maria.Grazia.Pia 2007-08-09 10:41:34 CEST
The problem is re-assigned to the developer specifically expert in this domain.

Maria Grazia Pia
Comment 2 alfonso.mantero 2007-08-28 19:45:40 CEST
The issue has been fixed, and will be released in the next release of Geant4.

Alf