Problem 2309 - ProcessSubType wiped out with emstandard_opt1
Summary: ProcessSubType wiped out with emstandard_opt1
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: physics_lists (show other problems)
Version: 10.6
Hardware: All All
: P4 major
Assignee: Vladimir.Ivantchenko
URL:
Depends on:
Blocks:
 
Reported: 2021-01-13 09:37 CET by Doris Kim
Modified: 2021-01-26 20:00 CET (History)
1 user (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 Doris Kim 2021-01-13 09:37:09 CET 
When "emstadard_opt1" aka "FTFP_BERT_EMV" gets invoked as the physics list, the ProcessSubType for the electromagnetic secondary tracks only show "fGammaGeneralProcess" instead of the correct physics process types such as "fGammaConversion".

> G4Track->GetCreatorProcess()->GetProcessSubType()

This problem happens only with FTFP_BERT_EMV. FTFP_BERT and other FTFP_BERT_EMx variants do not show this problem.
Comment 1 Vladimir.Ivantchenko 2021-01-13 09:41:05 CET 
Hi Gunter,

please, assign it to me.

Vladimir
Comment 2 Vladimir.Ivantchenko 2021-01-13 09:43:49 CET 
Hello,

the problem is known, the fix is available with Geant4 10.7. I do not know about plans for extra patch of 10.6.

VI
Comment 3 Doris Kim 2021-01-13 09:54:54 CET 
Hello,

     Thanks for the quick reply. Would it be possible to get a patch for this bug? However, currently we use version 10.6 patch 1 for our library.

Regards,
Doris
Comment 4 Doris Kim 2021-01-13 13:48:29 CET 
Or here is another idea. Would it be possible to know what caused the problem? Then I may try to fix the lines for our library of v10.6.

I checked the v10.7 release notes: It was listed that StepFunction() was fixed and the common parts of the StandardEM codes were replaced by G4EmBuilder().
Comment 5 Vladimir.Ivantchenko 2021-01-26 20:00:01 CET 
Hello,

General gamma process is used only in the EMV configuration. In Geant4 10.6 there was this known problem, which will be fixed in the 1st patch to 10.7 and will need a private patch for 10.6. I will send the updated code privately.

Vladimir