MCNP4 help: f4 tally in lattice

  • Thread starter Thread starter J_P_C
  • Start date Start date
  • Tags Tags
    Lattice
Click For Summary

Discussion Overview

The discussion revolves around troubleshooting an MCNP4 input file for modeling a 17x17 fuel element lattice, specifically focusing on calculating the average neutron flux in a designated pincell using an F4 tally. Participants explore issues related to tally configuration and input errors.

Discussion Character

  • Technical explanation
  • Debate/contested
  • Experimental/applied

Main Points Raised

  • One participant describes their attempt to model a fuel element and expresses confusion over an error message related to the F4 tally, indicating a lack of specified volume or area.
  • Another participant explains that the F4 tally measures total path length and divides it by the cell volume to calculate flux, suggesting that the error arises from the tally's inability to determine a finite volume due to the input structure.
  • It is proposed that adding "SD4 1" after the F4 tally could resolve the issue by explicitly specifying the divisor, although there are alternative suggestions to replace 1 with the actual volume or to redefine the tally cells.
  • A participant mentions that they encountered the same error despite implementing the suggested fix, leading to further inquiry about the correctness of the tally chain.
  • Another participant reports success in running the input file without modifications, suggesting that the issue may be related to the operating system or input file processing.
  • The original poster later confirms that their input file works after previously encountering errors, although they remain uncertain about the reason for the resolution.

Areas of Agreement / Disagreement

Participants express varying levels of understanding regarding the F4 tally and its configuration. While some agree on the necessity of specifying the divisor, others highlight potential differences in system compatibility affecting the input file's execution. The discussion does not reach a consensus on the underlying cause of the initial error.

Contextual Notes

Participants note that the issue may be influenced by the operating system used (Windows vs. Linux) and the specific version of MCNP4, which could affect how the input file is processed. There are also mentions of potential formatting issues in the input file that could lead to errors.

J_P_C
Messages
3
Reaction score
4
TL;DR
I can't find the way to correctly apply an f4 tally in a precise lattice position. Help please?
Hi all, I'm new to the forum. Maybe you guys can give me hand with this.

I am using MCNP4 to model a 17x17 fuel element. I want to know the average neutron flux in a specific pincell but so far everything I try results in error. This is my input (text file is attached too):
Code:
c CELL CARDS
1  1 -10.24  -7        u=1     imp:n=1         $Fuel
2  2 -6.504   7 -8    u=1     imp:n=1         $Clad
3  3 -1.000   8         u=1     imp:n=1         $Water outside clad
4  3 -1.00   -9         u=2     imp:n=1         $Water inside guide tube
5  2 -6.504   9 -10  u=2     imp:n=1         $Guide tube
6  3 -1.000   10       u=2     imp:n=1         $Water outside guide tube
7  0          3 -4 5 -6 lat=1  u=3  imp:n=1  $Fuel element lattice
              fill=-8:8 -8:8 0:0
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 1 1 2 1 1 2 1 1 2 1 1 1 1 1
              1 1 1 2 1 1 1 1 1 1 1 1 1 2 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 2 1 1 2 1 1 2 1 1 2 1 1 2 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 2 1 1 2 1 1 2 1 1 2 1 1 2 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 2 1 1 2 1 1 2 1 1 2 1 1 2 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 2 1 1 1 1 1 1 1 1 1 2 1 1 1
              1 1 1 1 1 2 1 1 2 1 1 2 1 1 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
              1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
8  0             11 -12 13 -14           fill=3  u=4  imp:n=1  $Fuel element
9  3   -1.0  -11:12:-13:14                        u=4  imp:n=1  $Water outside fuel element
10  0            1 -2 15 -16 17 -18  fill=4            imp:n=1  $Fuel element + water gap
999 0          -1:2:-15:16:-17:18                        imp:n=0  $Outside void

c SURFACE CARDS
*1  pz -200
*2  pz  200
 3  px -0.6325
 4  px  0.6325
 5  py -0.6325
 6  py  0.6325
 7  cz  0.4127 
 8  cz  0.4744
 9  cz 0.57294
 10 cz 0.61301
 11 px -10.7525
 12 px 10.7525
 13 py -10.7525 
 14 py 10.7525
*15 px -10.8055
*16 px 10.8055
*17 py -10.8055
*18 py 10.8055
I want to know the average neutron flux in the top right pincell.
I don't understand why the following tally results in the fatal error "tally volume or area was not input nor calculated":

f4:n ((1 2 3) < 7 [8 8 0] < 8 <10)

The way I see it all of my cells are finite when filled with their corresponding universes. I'm a bit lost right now. Any help is appreciated.
 

Attachments

Last edited by a moderator:
Engineering news on Phys.org
F4 is a flux tally, but instead of counting the neutrons going through it MCNP measures the total path length and divides it by the volume of the cell to calculate the flux. It's only the cookie cutting later that gives (1 2 3) finite volume. So the function to find the volume fails and MCNP freaks.

Fixed by specifying the divisor explicitly, which in this case is the volume. Adding "SD4 1" the line after the F4 tally causes it to run, either replace 1 with the real volume, do the division later or rewrite the tally cells to be bounded (the problem is neatly defined so I imagine you don't want to go this way).
 
  • Like
  • Informative
Likes   Reactions: J_P_C, Astronuc and berkeman
Alex A said:
F4 is a flux tally, but instead of counting the neutrons going through it MCNP measures the total path length and divides it by the volume of the cell to calculate the flux. It's only the cookie cutting later that gives (1 2 3) finite volume. So the function to find the volume fails and MCNP freaks.

Fixed by specifying the divisor explicitly, which in this case is the volume. Adding "SD4 1" the line after the F4 tally causes it to run, either replace 1 with the real volume, do the division later or rewrite the tally cells to be bounded (the problem is neatly defined so I imagine you don't want to go this way).
Thanks for the answer, I see what you mean. In fact, now that I know I need the sdn card I went looking into the manual and I saw that this card is especially recommended for tallies in repeated structures. I liked the idea of using the divisor just as 1 and dividing by the real value later, so I added the "sd4 1" line after the tally line, but still I get the same error. Maybe the chain of cells in the f4 tally is not correct? I am attaching the full, complete input to this message too.
 

Attachments

Your input file works unmodified for me with 4b under linux, I just renamed it to inp. I've run it with 4c but the binary was older and I needed to strip carriage returns (a linux thing). I assume you are in windows.

Try reading the output file to make sure the modification is in the input it is processing, for whatever reason. Check for any other errors or warnings. If it still doesn't work post the output file.
 

Attachments

  • Like
Likes   Reactions: berkeman
It finally works, although I have no idea why o0). I ran the very same input file from my previous message and this time it worked. And yes, I am in Windows. Thanks so much for the help!

My original intention was to compare the flux in an innmermost pincell versus flux in an outermost pincell. If by any chance anyone has my same problem in the future and finds the thread, the file I am attaching to this message is working and does what I intended.

Thanks again for the help.
 

Attachments

  • Like
Likes   Reactions: berkeman and Alex A

Similar threads

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