Problem 629 - Expose paramStepLimit in hLowEnergyIonisation?
Summary: Expose paramStepLimit in hLowEnergyIonisation?
Status: CLOSED INVALID
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/electromagnetic/lowenergy (show other problems)
Version: 6.1
Hardware: All All
: P2 enhancement
Assignee: Maria.Grazia.Pia
URL:
Depends on:
Blocks:
 
Reported: 2004-05-28 10:14 CEST by marcus.h.mendenhall
Modified: 2008-02-27 19:18 CET (History)
0 users

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 marcus.h.mendenhall 2004-05-28 10:14:47 CEST 
In hLowEnergyIonisation, the parameter paramStepLimit is declared as private and const, and initialised
to 0.005.  For many solid state applications, this is too low (it takes way too long to track a 2 MeV
proton down to rest).  Could this variable be declared as non-const, and then an accessor function
SetParamStepLimit(G4double limit) { paramStepLimit=limit; };
be added to the appropriate header file?

Thanks much.

Marcus Mendenhall
Comment 1 Maria.Grazia.Pia 2004-06-25 04:53:59 CEST 
The user requirement raised will be taken into account in a design iteration of
the Geant4 lowenergy package. Please note that design modifications to the
lowenergy package take place according to a controlled process, not just as
quick fixes proposed as a problem report. If you have new user requirements,
that are not satisfied by the present lowenergy code, please contact us
submitting your requirements, rather than a problem report.
Best wishes,
Maria Grazia Pia