MCNP lattice of the fuel assembly input file?

Click For Summary
SUMMARY

The forum discussion addresses an issue with a 16 x 16 lattice fuel assembly input file for MCNP (Monte Carlo N-Particle Transport Code). The primary error identified is related to the geometry definition, specifically the use of universe 0 fills, which creates undefined spaces outside the cooling tubes. The solution involves changing the universe 0 entries to universe 1 and correcting the lattice orientation from xz to xy. Following these adjustments, the input file successfully runs a kcode simulation.

PREREQUISITES
  • Understanding of MCNP (Monte Carlo N-Particle Transport Code) version 6 or later
  • Familiarity with lattice geometry definitions in nuclear engineering
  • Knowledge of universe fills and their implications in MCNP simulations
  • Experience with debugging input files and plotting geometries in MCNP
NEXT STEPS
  • Learn how to properly define universe fills in MCNP simulations
  • Research techniques for debugging MCNP input files effectively
  • Explore the use of the 'pz' command for plotting cross sections in MCNP
  • Investigate temperature settings and their impact on fuel assembly simulations in MCNP
USEFUL FOR

Nuclear engineers, MCNP users, and researchers involved in fuel assembly simulations will benefit from this discussion, particularly those troubleshooting geometry-related issues in their input files.

Islam Nabil
Messages
14
Reaction score
1
TL;DR
There is an input file of a simple lattice 16 x 16 fuel assembly. I have a message blocking the run of the code; bad trouble in subroutine newcel of mcrun source particle no 1 random number 6647299061401 zero lattice element hit. what is the wrong?
There is an input file for a simple 16 x 16 lattice fuel assembly. I have a message blocking the run of the code;
"bad trouble in subroutine newcel of mcrun source particle no 1 random number 6647299061401 zero lattice element hit."
What is wrong?
 

Attachments

Last edited:
Engineering news on Phys.org
There is an error somewhere in the geometry definition. If you change the filename of the input file to add .txt you can attach it to a post we can have a look at it.

If you can't share the input file you could try to debug it by plotting the geometry, but our help becomes very indirect.
 
Alex A said:
There is an error somewhere in the geometry definition. If you change the filename of the input file to add .txt you can attach it to a post we can have a look at it.

If you can't share the input file you could try to debug it by plotting the geometry, but our help becomes very indirect.
Upload the txt file ...
 

Attachments

Yes, if you click the button 'Attach files' you can find the file, if the name ends .txt
 
Alex A said:
Yes, if you click the button 'Attach files' you can find the file, if the name ends .txt
Already uploaded
 
Alex A said:
Yes, if you click the button 'Attach files' you can find the file, if the name ends .txt
Name changed
 
Sorry, maybe I needed to refresh the page or maybe I did not look at the first post!

Your lattice has universe 0 fills. I have not seen that before. You are cutting that out of the rpp being filled. Ok.

I did mcnp ip inp=file
Clicked to enter a command into the plot window and did,
pz 0
To see a cross section through the middle. Most fuel element positions are undefined. It will take me some time to look at this.
 
Firstly your lattice is xz instead of xy.
fill=-8:9 -9:8 0:0
not
fill=-8:9 0:0 -9:8

Secondly the 0 universe fill is creating a space outside your (cooling?) tubes that is not defined. Changing the universe 0 entries to universe 1 fixes that. That is the usual way to create a 'background' cell, refer the lattice universe to itself. I don't see any other problems at the moment. The geometry errors seem to have gone and the input file now runs a kcode.
 

Attachments

Alex A said:
Firstly your lattice is xz instead of xy.
fill=-8:9 -9:8 0:0
not
fill=-8:9 0:0 -9:8

Secondly the 0 universe fill is creating a space outside your (cooling?) tubes that is not defined. Changing the universe 0 entries to universe 1 fixes that. That is the usual way to create a 'background' cell, refer the lattice universe to itself. I don't see any other problems at the moment. The geometry errors seem to have gone and the input file now runs a kcode.
Thank you, thank you very much, Doctor... The problem has already been resolved... Thank you...
 
  • Like
Likes   Reactions: Alex A
  • #10
I'm not sure what your final objectives are, but this assembly is at room temperature.
I've attached an input for a 16x16 case that uses a fuel temperature of 900 K and all other
temperatures are set at 600 K.

Unfortunately, this doesn't use lattices and the pin diameters are slightly different from what you have.
 

Attachments

  • ce16-1.mcnp.txt
    ce16-1.mcnp.txt
    41.6 KB · Views: 192
  • ce16-1.png
    ce16-1.png
    17.5 KB · Views: 154
  • Like
Likes   Reactions: Islam Nabil and Alex A
  • #11
rpp said:
I'm not sure what your final objectives are, but this assembly is at room temperature.
I've attached an input for a 16x16 case that uses a fuel temperature of 900 K and all other
temperatures are set at 600 K.

Unfortunately, this doesn't use lattices and the pin diameters are slightly different from what you have.
Thanks a lot doctor... King regards
 

Similar threads

Replies
5
Views
2K
Replies
7
Views
3K
  • · Replies 8 ·
Replies
8
Views
2K
  • · Replies 1 ·
Replies
1
Views
3K
Replies
8
Views
3K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 15 ·
Replies
15
Views
3K
Replies
2
Views
885
  • · Replies 3 ·
Replies
3
Views
5K
Replies
2
Views
6K