Problem 1116 - Request for G4NeutronHPThermalScattering to have a name other than "HadronicModel"
Summary: Request for G4NeutronHPThermalScattering to have a name other than "HadronicM...
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic/models/neutron_hp (show other problems)
Version: 9.3
Hardware: All All
: P5 enhancement
Assignee: tkoi
URL:
Depends on:
Blocks:
 
Reported: 2010-05-12 16:13 CEST by Brian Fisher
Modified: 2010-07-30 00:03 CEST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description Brian Fisher 2010-05-12 16:13:39 CEST 
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.
Comment 1 tkoi 2010-07-30 00:03:12 CEST 
Add model name of "NeutronHPThermalScattering"