Problem 1155

Summary: neutron capture does not always produces the new (A->A+1) nucleus
Product: Geant4 Reporter: Cristian Bungau <cbungau>
Component: processes/hadronic/models/neutron_hpAssignee: tkoi
Status: RESOLVED FIXED    
Severity: trivial    
Priority: P5    
Version: other   
Hardware: All   
OS: All   

Description Cristian Bungau 2010-11-30 11:09:43 CET 
Hello,

I am simulating a 232ThO2 target (cylinder 90 cm long and radius = 30 cm) bombarded by 1 GeV protons and I am interested in the neutrons produced. Below is a summary of the neutron data I get:

7985 neutrons produced in inner volume.

1427 neutrons escaping inner volume.

4996 neutrons undergoing inelastic interactions inside inner volume.

119 neutrons producing fissions inside inner volume.

1443 neutrons captured inside inner volume.

64 (233Th) nuclei produced in the (1443) neutron capture processes inside inner volume.

Indeed the neutrons produced (7985) are equal to the sum of the rest: 1427+4996+119+1443.

The problem I encountered though was the fact that most of the neutron capture processes result in a single gamma emitted and NO 233Th isotope being produced. Only 64 out of the total of 1443 capture events result in 233Th being produced. I believe this should not be the case, please correct me if otherwise, so I decided to report this.

Thank you for looking into this,

Best regards,

Cristian
Comment 1 tkoi 2010-12-04 01:31:53 CET 
Hi Cristian

Thank you for reporting this problem

This problem is confirmed and fix is proposed. 
I hope the fix will be included coming release, but maybe not.
If you voluntary test the fix, please contact me directly. 

Tatsumi
Comment 2 Cristian Bungau 2010-12-07 12:04:44 CET 
(In reply to comment #1)

Dear Tatsumi,

Thank you very much for your reply regarding this problem and for taking the time to look into it. I would be very grateful if you could please de send me the fix so I can test it as well and apply it to my simulations.

Thank you,

Best regards,

Cristian


> Hi Cristian
> 
> Thank you for reporting this problem
> 
> This problem is confirmed and fix is proposed. 
> I hope the fix will be included coming release, but maybe not.
> If you voluntary test the fix, please contact me directly. 
> 
> Tatsumi