Discussion Overview
The discussion revolves around an error encountered in MCNP simulations, specifically the "geometry error: no intersection found" message. Participants explore potential causes related to cell definitions and overlaps in the geometry setup, focusing on the implications of infinite volumes in certain cells.
Discussion Character
- Technical explanation
- Debate/contested
Main Points Raised
- One participant notes that cell 14 is outside of two RCC surfaces and extends to infinity, raising questions about its importance and the comment indicating it is "outside of problem."
- Another participant points out that cell 22 also extends to infinity due to being outside surface 10 and suggests that it has overlaps with other cells.
- Concerns are raised about the use of the # operator in defining cells, with a recommendation to simplify cell definitions by identifying inner and outer surfaces instead.
- It is proposed that splitting cell 22 into three parts based on different radii could help eliminate the need for the # operator and potentially improve simulation performance.
- Participants discuss the use of sub-surfaces of RCCs for defining cells, noting the peculiarities in coordinate directions for the top and bottom surfaces.
Areas of Agreement / Disagreement
Participants express various viewpoints on the geometry setup and potential solutions, indicating that multiple competing views remain regarding the best approach to resolve the error.
Contextual Notes
There are unresolved aspects regarding the implications of using the # operator and the specific configurations of the cells, which may affect the simulation outcomes.