| Summary: | Different DNA options never used | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | alantarx |
| Component: | processes/electromagnetic/dna | Assignee: | Sebastien Incerti <incerti> |
| Status: | RESOLVED LATER | ||
| Severity: | minor | CC: | incerti, Koichi.Murakami |
| Priority: | P4 | ||
| Version: | 10.5 | ||
| Hardware: | All | ||
| OS: | All | ||
This feature for other constructors is expected to be added in the future. |
In documentation, the command-line option "/process/em/AddDNARegion {regname} DNA_Opt{#} is given, where # may presumably be filled in with any of the options given in the source: 1-7. However, in "G4EmDNAPhysicsActivator.cc", which documentation suggests is to be used with this, theParameters->TypesDNA() is invoked but on lines 385-387 "itype" is simply set to 0 regardless of the value in typesDNA[i] and the local processes are invoked. I found this attempting to use the command line option and G4EmDNAPhysicsActivator to set the DNA physics for a specific region and attempting to use different options to test the relative efficiency and accuracy. After enough data accumulated, I realized there were no statistically significant differences in either case. I have found the following work-around: Invoking options in userPhysicsListMessenger as in /medical/dna/microyz example.