Cones in MCNP can be defined with a cut flag. This chooses the plane that the cone is active on. It is the same as adding a plane at the cone origin and selecting a side. After any rotation that leaves the cone axis out of the XYZ axis of the output model, the code has to be represented as a general quadratic surface. This results in the requirement to add an extra plane.
From now on the use of the cut flag will not be supported in the master branch. [You are welcome to use it in your local models]. I have decided that all such cones in the master model will have the plane added initially and the model adjusted so all rotations are valid.
The main place that needed fixing was in BasicFlightLine.cxx, and further in the derived class for the ESS (WedgeFlightLine.cxx).
Cones in MCNP can be defined with a cut flag. This chooses the plane that the cone is active on. It is the same as adding a plane at the cone origin and selecting a side. After any rotation that leaves the cone axis out of the XYZ axis of the output model, the code has to be represented as a general quadratic surface. This results in the requirement to add an extra plane.
From now on the use of the cut flag will not be supported in the master branch. [You are welcome to use it in your local models]. I have decided that all such cones in the master model will have the plane added initially and the model adjusted so all rotations are valid.
The main place that needed fixing was in BasicFlightLine.cxx, and further in the derived class for the ESS (WedgeFlightLine.cxx).
Any problems please let me know.