Hi, I am running into an issue with defining more than 16 scoring meshes. The issue is outlined in this forum post: https://geant4-forum.web.cern.ch/t/cannot-add-more-than-16-scoring-meshes/5465 Since I was not able to receive a definite answer on the forum, I'm posting the issue here. I'd like to know if having a maximum of 16 scoring meshes is intended behavior or it is an actual bug? If the behavior is intended it is reasonable to mention about it in User Documentation: https://geant4-userdoc.web.cern.ch/UsersGuides/ForApplicationDeveloper/html/Detector/commandScore.html
16 is not necessarily the exact limit, but we do not expect to have unlimited number of parallel worlds. If your meshes are not overlapping to each other, I suggest you to implement such meshes in one parallel world. It would be much better in computing performance.
Hi, thanks for your reply. In order to implement the meshes we used the approach described in the following Geant4 example: https://github.com/Geant4/geant4/blob/master/examples/extended/runAndEvent/RE03/run1.mac Our meshes are not overlapping with each other. Can you please clarify how to define all the meshes in one parallel world? And why by default meshes are defined in parallel worlds? Below is a piece of the code used to create the meshes: ######################################## # /score/create/boxMesh boxMesh_1 # /score/mesh/boxSize 30. 30. 1. cm /score/mesh/translate/xyz 0. 0. -80. cm /score/mesh/nBin 20 20 20 # /score/quantity/nOfStep nOfStepGamma /score/filter/particle gammaFilter gamma # /score/close # ######################################## # /score/create/boxMesh boxMesh_2 # /score/mesh/boxSize 30. 30. 1. cm /score/mesh/translate/xyz 0. 0. -75. cm /score/mesh/nBin 20 20 20 # /score/quantity/nOfStep nOfStepGamma /score/filter/particle gammaFilter gamma # /score/close # ######################################## ...<more meshes defined the same way>
