| Summary: | Expose paramStepLimit in hLowEnergyIonisation? | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | marcus.h.mendenhall |
| Component: | processes/electromagnetic/lowenergy | Assignee: | Maria.Grazia.Pia |
| Status: | CLOSED INVALID | ||
| Severity: | enhancement | ||
| Priority: | P2 | ||
| Version: | 6.1 | ||
| Hardware: | All | ||
| OS: | All | ||
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 |
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