Did Installing ENDFVII Fix the MCNP5 Error in Routine IMCN?

Click For Summary
SUMMARY

The installation of ENDF VII has been confirmed to resolve the MCNP5 error encountered in routine IMCN, specifically the "bad trouble in imcn" error related to memory issues. Users have reported that correcting trailing spaces and ensuring proper comment formatting in the input file can also mitigate similar errors. The discussion highlights the importance of using compatible libraries, as ENDF VIII may introduce compatibility issues with older MCNP5 versions. The version used in successful tests was MCNP5.1.60 on a Linux operating system.

PREREQUISITES
  • Familiarity with MCNP5 simulation software
  • Understanding of ENDF VII and ENDF VIII libraries
  • Knowledge of input file formatting and syntax for MCNP5
  • Basic troubleshooting skills for software errors
NEXT STEPS
  • Research the installation process for ENDF VII and its compatibility with MCNP5
  • Learn about common MCNP5 error messages and their resolutions
  • Explore input file formatting best practices for MCNP5
  • Investigate the differences between ENDF VII and ENDF VIII libraries
USEFUL FOR

Researchers, physicists, and engineers using MCNP5 for simulations, particularly those troubleshooting errors related to input file formatting and library compatibility.

Limitzone
Messages
2
Reaction score
0
TL;DR
i am getting an error which reas as follows :
bad trouble in imcn in routine imcn source particle no error getting memorybly a control character,in coulumn 32
mcnp5
 
Engineering news on Phys.org
Have you tried to use google to search on the text of the error message?

mncp5 error: bad trouble in imcn in routine imcn source particle no error getting memorybly a control character,in coulumn 32

Sometimes other folks have had the same issue and you may find a solution.

We also have several threads at PF (shown below on the web page) where posters had similar problems with mncp5.
 
@Limitzone
Rename your output file to add .txt to the end, then attach it to a post.
 
okey thank you bro
 

Attachments

While I'm not familiar with MNCP5, I looked through your file and noticed a few non-comment lines that had trailing spaces. There were a few lines with $ comments I think with trailing spaces too but I didn't think they would cause a problem.

See lines 85, 86 below which have an extra space at the end:

Code:
        40091.81c -1.10237E-01
        40092.81c -1.68499E-01

Could trailing spaces on your input cards cause the error you see?

I also saw a few blank lines, at lines 44, 59, 110, and 111. Should they instead be comment lines ie start with a "c"?

Lastly, should line #2 be a comment line eg c234567890123456789012 which I assume you added to locate column 32.
 
When I change line 2 to
Code:
c 345678901234567890123456789012
the only thing that stops me running it is that I don't have ENDF VIII installed. When I make the changes to get it to run with the library native to 5, ENDF VI, (I removed .81c from the end of materials, and tin entirely), it just runs fine and gives a keff of 1.28.

Your actual error is strange btw, if it's 100% char for char your error. It looks like two normal MCNP5 errors smashed into one another. Reading the output file may provide more detail. I did ask for that, not the input file btw :) My thoughts now are maybe ENDF VIII is so new it's breaking the old MCNP 5 code. I may try installing ENDF VIII, but it needs a lot of disc space. Long and painful past experience makes me not trust very new libraries with old code. What version of 5 are you using and in what OS? It is also possible it's a linefeed or carriage return code issue which might be OS dependent. I ran with 5.1.60, which was the last release of 5, in linux.

@jedishrfu Just an FYI, the first two blank lines, in this case at 44 and 59, tell MCNP when the cell section and surface section end. Some aspects are quite arcane.
 
  • Like
Likes   Reactions: jedishrfu
.81c turns out to be ENDFVII, not VIII and I installed that. All the libraries can just be downloaded from here if anyone wants them.
With only the "c 3" change 5.1.60 is working so my main thought wasn't right.
 

Similar threads

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