Problem 1853 - G4HadronElasticPhysicsPHP fail in multi-threaded application.
Summary: G4HadronElasticPhysicsPHP fail in multi-threaded application.
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: physics_lists (show other problems)
Version: 10.2
Hardware: All All
: P5 trivial
Assignee: Alberto.Ribon
URL:
Depends on:
Blocks:
 
Reported: 2016-04-08 15:17 CEST by John Watts
Modified: 2016-05-31 17:54 CEST (History)
3 users (show)

See Also:

Attachments
G4HadronElasticPhysicsPHP tar ball (1.62 KB, application/x-gzip)
2016-04-08 15:17 CEST, John Watts 		Details
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 John Watts 2016-04-08 15:17:47 CEST 
Created attachment 395 [details]
G4HadronElasticPhysicsPHP tar ball

When G4HadronElasticPhysicsPHP is used in a multi-threaded application it fails with the message:

-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : Run0035
issued by : G4RunManagerKernel::G4RunManagerKernel()
Size of G4ProcessVector is inconsistent between master and worker threads
for the particle <B+>.
size of G4ProcessVector for worker thread is 4 while master thread is 5.
*** Fatal Exception *** core dump ***
----------------------------------------------------
By comparing it with G4HadronElasticPhysicsHP I concluded the the variables:
wasActivated, and mainElasticBuilder were not used correctly and modified the code based on how these variables are used in G4HadronElasticPhysicsHP.
Attached is the modified source.
Comment 1 Alberto.Ribon 2016-05-31 17:54:36 CEST 
Yes, you are right. The problem has been fixed in our development line, and will be included in the coming beta release, G4 10.3beta, expected by the end of June.

Thanks!