"10 particles lost" warning in MCNPX

  • Thread starter Thread starter Nour_wahban
  • Start date Start date
  • Tags Tags
    Error Mcnp Mcnpx
Click For Summary

Discussion Overview

The discussion revolves around troubleshooting a "10 particles lost" warning in MCNPX simulations, specifically related to modeling a neutron detection setup involving a point source, backscattered neutrons, and the configuration of various detector components. Participants explore issues with statistical checks, detector definitions, and output discrepancies, focusing on both theoretical and practical aspects of the simulation.

Discussion Character

  • Technical explanation
  • Debate/contested
  • Mathematical reasoning
  • Experimental/applied

Main Points Raised

  • Some participants suggest that the point source should not coincide with a surface, recommending a slight adjustment to the source position to avoid errors.
  • There are concerns about the definitions of the BPE and PE components, with some participants proposing that they were initially swapped in the input file.
  • Statistical errors are noted as potentially indicating that too few particles are reaching the detector, with suggestions to increase the number of particles simulated to improve statistical reliability.
  • One participant expresses confusion over the output flux values, questioning why there is little change in flux with and without TNT, suggesting that the model may not be accurately capturing backscattered neutrons.
  • Another participant mentions the need for a new tally to differentiate between elastic and inelastic scattered neutrons, indicating a limitation in the current model setup.
  • There is a discussion about the capabilities of the detector and how it might differentiate neutron types based on energy and flux, referencing a paper that implies a more sophisticated detection method.
  • Participants express a desire for feedback on their updated input files and plots related to flux versus energy.

Areas of Agreement / Disagreement

Participants do not reach a consensus on the cause of the warnings or the best approach to resolve the issues. Multiple competing views and suggestions remain, particularly regarding the configuration of the detector and the interpretation of output results.

Contextual Notes

Limitations include unresolved statistical checks, potential misconfigurations in the input file, and the challenge of accurately modeling neutron interactions in the presence of different materials. The discussion highlights the complexity of differentiating neutron types in the simulation.

Nour_wahban
Messages
5
Reaction score
0
TL;DR
hello! i'm working on a landmine detection using neutron technique and the model involves using a ring detector i did my best to understand its part but i'm getting this error and the tally counts are not correct. I attached the input file if someone could help!
model fig.jpg
 

Attachments

Engineering news on Phys.org
Welcome to PhysicsForums @Nour_wahban,

The source is at 0 53 0. Surface 20 is defined as py 53. Never make a point source coincident with a surface. Even surfaces made by a macrobodies and even when they extend beyond the cell they define. Changing to POS=0 52.5 0 solves that error for me. I do not know how ring detectors work, if the tally is still wrong post more information and hopefully someone will know.

Suggest you define the void as "3 0 23", just because it's simpler.

Edit, btw your BPE doesn't surround your PE moderator, how big are the BPE and PE supposed to be?
 
  • Informative
Likes   Reactions: Nour_wahban
Alex A said:
Welcome to PhysicsForums @Nour_wahban,

The source is at 0 53 0. Surface 20 is defined as py 53. Never make a point source coincident with a surface. Even surfaces made by a macrobodies and even when they extend beyond the cell they define. Changing to POS=0 52.5 0 solves that error for me. I do not know how ring detectors work, if the tally is still wrong post more information and hopefully someone will know.

Suggest you define the void as "3 0 23", just because it's simpler.

Edit, btw your BPE doesn't surround your PE moderator, how big are the BPE and PE supposed to be?
Thank you for the reply, I edited the part of the source, and it works now but still gives me a tally warning "
warning. tally 4 tfc bin did not pass 2 of 10 statistical checks.
warning. 1 of 1 tallies did not pass all 10 statistical checks.
warning. 1 of 1 tallies had bins with large relative errors. "
for the part of BPE it should 5 cm radius with 2.5 cm height while PE is 2.5 cm radius and 5 cm height.

The model goal is to count back scattered neutrons on the ring detector and I'm still struggling how to model this properly.

EDIT, I changed the tally to f4 and added a ring detector cell since the output of f5 is not working properly. but unfortunately, it's not giving me a correct output also. I attached an image with the curve i'm trying to plot to validate this model and the new input file.
 

Attachments

Last edited by a moderator:
"17 cy 5 $PE
18 cy 2.5 $BPE"
These definitions are backwards, swap 17 and 18. This probably isn't the cause of your problems.

Statistical errors are usually an indication too few particles are making it to the detector. Having multiple rings in the problem and running a higher nps might help to get a lot of results with the same compute and better stats.

What are your results and how are you working out the answer?
 
  • Like
Likes   Reactions: Nour_wahban
For the part of BPE and PE I switched them in my reply. They are written correctly in the input file and the image I attached.

I want to see the change in the flux with and without the TNT, but in the output flux doesn't change. It gives me 1.5*10^-3 with the TNT and 1.49*10-3 without it. I cannot understand what's the reason for this output it seems like it cannot see the TNT or it is counting the flux coming from the source not the backscattered.
EDIT: (I'm trying to calculate signal to background ratio, and it should be near 8 but with this output it is about 0.1)
Btw I'm trying to add the output files but their extensions are not acceptable here.
 
Last edited:
A text file needs to be changed to have a .txt extension. Then you should be able to attach, so long as it isn't too big.

"17 cy 5 $PE
18 cy 2.5 $BPE"
Still seems to be the wrong way round to me, 18 is BPE but it should be 5, 17 is PE but it should be 2.5.

The paper says this "The EBS neutrons can be detected by a suitable detector capable of differentiating the EBS neutrons according to their energy and their flux.", which suggests that the detector is perhaps a bit more clever than most real world detectors. It hints that they have determined what counts as a thermal neutron by what gives the best result. Do you have a plot of flux versus energy with and without the mine?
 
Actually, it seems to be wrong for me as well, but I'm following the procedures to validate the model.

For the part of detector my conclusion was that he used ring detector tally f5 instead of defining it in a separate cell.
another thing is the EBS neutrons the flux doesn't differentiate between elastic and inelastic scattered neutrons and i think this is one of the drawbacks of my input file the counts are not for EBS neutrons only.

I have added a new tally CF4 to count only the neutrons after they reach cell 1 or 2 (soil and TNT) I don't know other ways to differentiate them in MCNP. I will attach the updated input file with the output files and the plots I got of flux versus energy. If you have any comments or conclusions on them, please let me know.
Thank you so much for your assistance.
 

Attachments

  • without TNT with shield.jpg
    without TNT with shield.jpg
    42.6 KB · Views: 79
  • TNT without shield.jpg
    TNT without shield.jpg
    51 KB · Views: 53
  • TNT with shield.jpg
    TNT with shield.jpg
    48.3 KB · Views: 46
  • mymodelwithout.txt
    mymodelwithout.txt
    1.4 KB · Views: 48
  • phyf.txt
    phyf.txt
    49.2 KB · Views: 49
  • phyf2.txt
    phyf2.txt
    48.3 KB · Views: 59
  • phyf3.txt
    phyf3.txt
    49.1 KB · Views: 56

Similar threads

  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 4 ·
Replies
4
Views
3K
Replies
3
Views
2K
  • · Replies 15 ·
Replies
15
Views
3K
  • · Replies 5 ·
Replies
5
Views
3K
Replies
6
Views
7K
Replies
5
Views
990
Replies
2
Views
2K
Replies
1
Views
3K