Problem 2114 - Different DNA options never used
Summary: Different DNA options never used
Status: RESOLVED LATER
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/electromagnetic/dna (show other problems)
Version: 10.5
Hardware: All All
: P4 minor
Assignee: Sebastien Incerti
URL:
Depends on:
Blocks:
 
Reported: 2019-01-10 01:42 CET by alantarx
Modified: 2019-01-10 10:20 CET (History)
2 users (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 alantarx 2019-01-10 01:42:31 CET 
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.
Comment 1 Sebastien Incerti 2019-01-10 08:39:39 CET 
This feature for other constructors is expected to be added in the future.