Necessary Maintenance #20029
SimpleBoundary() should be moved from DetectorProperties to LArProperties
SimpleBoundary() is used to decide whether to use the reflection simulation out of GEANT4 or if instead use a "simple boundary" simulation which includes a specular and a diffuse reflectivity part.
All the reflectivity parameters are stored in
detinfo::LArProperties, but the
SimpleBoundary() method is in
The method should be moved to
#1 Updated by Gianluca Petrillo over 2 years ago
The standard way LArSoft used to approach this type of migrations is two-steps:
- deal with the originating ticket (this one):
- announce the coming change and deprecation at the LArSoft coordination meeting
- copy the method in the new position
- modify the method in the old position to refer to the new one (when possible), and decorate the former as
- create a ticket following this one by one month or so, whose resolution will consist in removing the deprecated method
- mark the original issue (this one) as resolved
- after the established time, deal with the second ticket, either:
- ask permission:
- announce in the LArSoft coordination meeting that with the next version the deprecated method will be removed, and ask for objections
- eventually remove the deprecated method in the next release
- ask forgiveness:
- remove the deprecated method in the next release
- announce the breaking change in the next LArSoft coordination meeting
- ask permission:
#5 Updated by Hans-Joachim Wenzel over 2 years ago
I think the change is not necessary. In the refactored larg4 module all the optical processes including reflection are handled by the Geant4 optical processes. In the new scheme the properties of reflective surfaces are described in the gdml file (currently there are only 2 materials for which this is relevant). We just have to find the find the geant4 process and settings which closests represent the simple boundary process and add it to the gdml file.
#6 Updated by Gianluca Petrillo over 1 year ago
I am not the expert of this simulation, but my understanding is that
SimpleBoundary() is the handle for an option.
Are you suggesting that this option should be controlled in the GDML detector geometry description file, and that therefore an experiment has to hard-code and stick to one option?