Why am I getting a fatal error in MCNP with xsdir missing cross-section tables?

  • Thread starter Thread starter DanatAMFL
  • Start date Start date
  • Tags Tags
    Error Mcnp
Click For Summary
SUMMARY

The discussion centers on a fatal error encountered in MCNP5 version 1.60, specifically indicating that cross-section tables are missing from the xsdir file. The user attempted to resolve this by creating a symbolic link to a custom cross-section directory using the command ln -s /file/path/to/LANL/MCNP_DATA/mycustomxsectiondirectory xsdir. Despite ensuring that the DATAPATH and PATH variables are correctly set in both the .bashrc and .bash_profile files, the error persists even when using the default xsdir file. This indicates a potential misconfiguration or missing files in the MCNP installation.

PREREQUISITES
  • Understanding of MCNP5 version 1.60 and its file structure
  • Familiarity with symbolic links in Unix/Linux systems
  • Knowledge of environment variables such as DATAPATH and PATH
  • Basic troubleshooting skills for software installation issues
NEXT STEPS
  • Verify the contents of the custom cross-section directory against the default xsdir file
  • Learn how to troubleshoot symbolic links in Unix/Linux
  • Research the correct configuration of environment variables for MCNP5
  • Explore the MCNP5 documentation for common installation issues and solutions
USEFUL FOR

This discussion is beneficial for nuclear engineers, computational physicists, and researchers using MCNP5 for simulations who are facing configuration issues related to cross-section data files.

DanatAMFL
Messages
7
Reaction score
0
fatal error. *** cross-section tables are missing from xsdir
10001.70m
10002.70m
10003.70m
...
bad trouble in subroutine ixsdir of imcn
cannot continue with missing cross-section table(s).

is the message I am getting. I have created a link using

ln -s /file/path/to/LANL/MCNP_DATA/mycustomxsectiondirectory xsdir

to direct MCNP to my custom x-section directory when it is looking for xsdir. The custom directory is identical to the xsdir file created during the mcnp install, aside from the names of the libraries. The custom libraries that are listed in the directory are in the same folder with the rest of the libraries from MCNP. My DATAPATH and PATH variables are set to the correct locations in both my .bashrc and .bash_profile files.(DATAPATH is set to the /LANL/MCNP_DATA folder and path is set to the /MCNP5/bin folder) I tried using the default xsdir file to see if it was an issue with my custom directory, and it gave me the same error. I'm not sure why it is giving me this error. It is MCNP5 ver. 1.60. Thanks for any help!
 
Engineering news on Phys.org
Any solutions?

regards.
 

Similar threads

  • · Replies 11 ·
Replies
11
Views
11K
  • · Replies 1 ·
Replies
1
Views
5K