| Summary: | Request for G4NeutronHPThermalScattering to have a name other than "HadronicModel" | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Brian Fisher <bmfisher> |
| Component: | processes/hadronic/models/neutron_hp | Assignee: | tkoi |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | bmfisher |
| Priority: | P5 | ||
| Version: | 9.3 | ||
| Hardware: | All | ||
| OS: | All | ||
Add model name of "NeutronHPThermalScattering" |
Currently G4NeutronHPThermalScattering inherits from G4HadronicInteraction. However its modelName member is set to the default "HadronicModel" from G4HadronicInteraction, as you can see from its default constructor: G4NeutronHPThermalScattering::G4NeutronHPThermalScattering() This is unlike the constructor for G4NeutronHPElastic: G4NeutronHPElastic::G4NeutronHPElastic():G4HadronicInteraction("NeutronHPElastic") Having a distinctive name eases the understanding of the verbose output of the Hadronic Processes Summary, such as: G4HadronicProcessStore::Instance()->Dump(1); Could the modelName member for G4NeutronHPThermalScattering be set to something like "NeutronHPThermalScattering"? Thanks.