Discussion Overview
The discussion revolves around issues encountered while inputting voxel arrays and their universes in MCNP (Monte Carlo N-Particle Transport Code). Participants share specific error messages and seek assistance with geometry errors, cell definitions, and surface types.
Discussion Character
- Technical explanation
- Debate/contested
- Homework-related
Main Points Raised
- One participant reports an error related to an unrecognized surface type when defining a voxel universe, suggesting a potential formatting issue.
- Another participant indicates that a "zero lattice element hit" error typically signifies geometry errors, overlapping cells, or mis-defined surfaces.
- A participant expresses a similar issue with a "bad trouble in subroutine newcel" error, suspecting it relates to repeated surface definitions in the geometry chain.
- One user encounters a "cell 2 have no fill" error while attempting to run their code, indicating a possible issue with cell definitions or fills.
Areas of Agreement / Disagreement
Participants express various problems and potential solutions, but no consensus is reached on the specific causes or resolutions for the errors discussed. Multiple competing views on the nature of the errors and their solutions remain present.
Contextual Notes
Participants reference external resources, such as a primer on common MCNP problems, but some links provided are reported as non-functional. The discussion includes unresolved technical details and assumptions about the geometry definitions.
Who May Find This Useful
This discussion may be useful for users of MCNP who are facing similar issues with voxel arrays, geometry definitions, or error troubleshooting in their simulations.