I have met several minor bugs during my use of iWW-GWR and here I suggest a solution to fix them.
When weight window data is saved to VTK, data axes are stored in a wrong order. It is illustrated on the screenshots below. The upper figure shows the vertical cross-section of weight-windows generated by the original code (however, data order in MCNP WW file is correct). So I suggest to swap x and z axes during data export to VTK format. The result after axes swap is shown on the bottom figure.
Mesh location both in VTK and WW is shifted to the origin, at least for cartesian coordinate system. The error is introduced during meshtal file reading. When I fixed mesh values in WW file manually, all readings and writings were correct. The figure below shows by solid color WW mesh, and meshtally by wireframe. To fix this origin is not subtracted from mesh bin boundaries any more.
I have met several minor bugs during my use of iWW-GWR and here I suggest a solution to fix them.
When weight window data is saved to VTK, data axes are stored in a wrong order. It is illustrated on the screenshots below. The upper figure shows the vertical cross-section of weight-windows generated by the original code (however, data order in MCNP WW file is correct). So I suggest to swap x and z axes during data export to VTK format. The result after axes swap is shown on the bottom figure.
Mesh location both in VTK and WW is shifted to the origin, at least for cartesian coordinate system. The error is introduced during meshtal file reading. When I fixed mesh values in WW file manually, all readings and writings were correct. The figure below shows by solid color WW mesh, and meshtally by wireframe. To fix this origin is not subtracted from mesh bin boundaries any more.
Minor fixes in README and .gitignore.