Where Are the Other Detectors for F5 Tally in MCNP?

Click For Summary
SUMMARY

The discussion centers on the functionality of multiple detectors for F5 tallies in MCNP (Monte Carlo N-Particle Transport Code), specifically versions 6.2 and 6.3. Users have noted that while the MCNP manual allows for multiple detector locations within a single F5 tally, only the first detector's results appear in the output file. The remaining results are stored in the .m file, which is identified as the MCTAL file. The conversation highlights the limitations of the MCNP code, particularly its user-unfriendliness and outdated FORTRAN syntax, while confirming that F15, F25, and F35 can be used separately for distinct outputs.

PREREQUISITES
  • Understanding of MCNP 6.2 and 6.3 functionalities
  • Familiarity with F5 tally and detector concepts in MCNP
  • Basic knowledge of FORTRAN programming language
  • Awareness of MCTAL file structure and usage
NEXT STEPS
  • Research the differences between MCNP5 and MCNP6 regarding tally functionalities
  • Explore the use of the 'ND' keyword in MCNP for suppressing tally results
  • Learn about the structure and interpretation of MCTAL files in MCNP
  • Investigate user-friendly alternatives or updates for MCNP software
USEFUL FOR

This discussion is beneficial for nuclear engineers, radiation physicists, and researchers utilizing MCNP for particle transport simulations, particularly those seeking to optimize tally configurations and improve output clarity.

Will_007
Messages
6
Reaction score
1
TL;DR
where is the output for multiple F5 tally detectors
The MCNP manual states that you can have multiple detectors for a single F5 tally. Say you have f15:n x1 y1 z1 r x2 y2 z2 r.....Thing is, my output file only lists the tally result for the first f5 detector (x1,y1,z1). Where are other detectors for this tally? Is there a reason code developers enabled this method of defining multiple detectors vs just using f15, f25, f35....for each one?

Thanks,
Will
 
Engineering news on Phys.org
f15, f25, f35 should all work and give separate answers, I wonder if you specify multiple rings or points on the same tally if it sums all the calculations to a single answer. I might do a test. I'd say the code is not 'clever' but internally it's extremely clever. What it's not is user friendly. It's derived from an old code and it's still in FORTRAN, which has limited string handling capabilities, everything has to be quite explicit; syntax is fairly brittle and error checking is woefully lacking.
 
Hey Alex - so yes, F15, F25....can be used separately but this option allows you to use F15 and then list multiple detector locations (not ring or a sum...the results appear to be as if you separately assigned a tally number to each). Discussion in the manual is limited, but in latest manual online (MCNP 6.3), this is the statement below. It looks like only the first detector belonging to the tally is in the output file, the rest are in the .m file but minimal labels (not user friendly at all)
1675206546484.png
 
I have almost no experience with MCNP6, so I've done some reading. There also isn't much in the way of a glossary. I understand a tally is an F card, a bin is when it's split into multiple results by energy, position or time and a detector is an object that has to be inserted in addition to the existing geometry and cell cards.

F1,2,3,4,6 and 7 don't involve detectors, they use an existing object. MCNP5 and later allows many objects on the same tally and how the results are shown depends upon parentheses.

MCNP5 only allows one ring or point per tally but the same note is in the MCNP5 manual, just meaning F5 can do point arrays (and maybe other reasons) so don't expect to do 20 (the detector limit for that version) F5 tallies under all circumstances.

X 2.6.0, 6.2 and 6.3 manuals allow multiple ring and point detectors per tally and the expected behavior is that is write a tally total as well as individual results for each detector unless this is suppressed with the 'ND' keyword.

The 6.1 and 6.1.1 manuals are maybe unhelpful, and they appear to be derived from the MCNP5 manual, so the behavior might not match the code.

So yeah, unless you are using the 'ND' keyword you should see a result for every detector on the line according to the manual. I also have no idea what the .m file is. :)
 
  • Like
Likes   Reactions: Will_007
thanks - .m file is the MCTAL file (obviously! :) )...one day when LANL makes this a user-friendly code it will transform it from formula one to bentley
 
  • Like
Likes   Reactions: Alex A

Similar threads

  • · Replies 1 ·
Replies
1
Views
3K
  • · Replies 1 ·
Replies
1
Views
4K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 14 ·
Replies
14
Views
4K
  • · Replies 14 ·
Replies
14
Views
2K
  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 7 ·
Replies
7
Views
4K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 7 ·
Replies
7
Views
2K
  • · Replies 4 ·
Replies
4
Views
4K