Problem 1930 - Inconsistency in candidate names for msc1Cmd in G4EmParametersMessenger.cc
Summary: Inconsistency in candidate names for msc1Cmd in G4EmParametersMessenger.cc
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/electromagnetic (show other problems)
Version: 10.2
Hardware: All All
: P4 minor
Assignee: Vladimir.Ivantchenko
URL:
Depends on:
Blocks:
 
Reported: 2016-12-14 13:44 CET by Iwan Cornelius
Modified: 2016-12-14 17:38 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 Iwan Cornelius 2016-12-14 13:44:01 CET 
Hello,

In the following class definition:

geant4.10.02.p02/source/processes/electromagnetic/utils/src/G4EmParametersMessenger.cc

There is a very minor issue with the naming of candidates between these two commands. The latter is inconsistent with the former, as well as the online documentation here:

https://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/ForApplicationDeveloper/html/AllResources/Control/UIcommands/_process_msc_.html

mscCmd = new G4UIcmdWithAString("/process/msc/StepLimit",this);
mscCmd->SetGuidance("Set msc step limitation type");
mscCmd->SetParameterName("StepLim",true);
mscCmd->SetCandidates("Minimal UseSafety UseSafetyPlus UseDistanceToBoundary");
mscCmd->AvailableForStates(G4State_PreInit,G4State_Idle);

msc1Cmd = new G4UIcmdWithAString("/process/msc/StepLimitMuHad",this);
msc1Cmd->SetGuidance("Set msc step limitation type for muons/hadrons");
msc1Cmd->SetParameterName("StepLim1",true);
msc1Cmd->SetCandidates("fMinimal fUseSafety fUseSafetyPlus fUseDistanceToBoundary");
msc1Cmd->AvailableForStates(G4State_PreInit,G4State_Idle);


Best regards, 
Iwan
Comment 1 Vladimir.Ivantchenko 2016-12-14 17:38:25 CET 
Hello Iwan,

thanks you very much for finding the problem. It was already fixed in Geant4 10.3 and the fix will be backported to the new patch to 10.2.

VI