Problem 504 - Infinite loop in G4StatMFMicroPartition.cc
Summary: Infinite loop in G4StatMFMicroPartition.cc
Status: CLOSED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic/models (show other problems)
Version: other
Hardware: PC Linux
: P1 minor
Assignee: Vicente.Lara
URL:
: 545 546 (view as problem list)
Depends on:
Blocks:
 
Reported: 2003-07-07 10:42 CEST by Fan.Lei
Modified: 2012-02-15 05:10 CET (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description Fan.Lei 2003-07-07 10:42:15 CEST
While simulating 10s of MeV proton incident on to C and Si target, the
execution runs into an infinite loop in the G4StatMFMicroPartition.cc (the
while loop at lines 191:193, with Db being negative all the time and eventually
becomes -inf).
Comment 1 Hans-Peter.Wellisch 2003-07-08 03:41:59 CEST
Hi Vicente,

 can you have a look at this?

Many greetings,

Hans-Peter.
Comment 2 Vicente.Lara 2003-10-21 13:14:59 CEST
The problem report is not very helpful. I've not been able to reproduce the
problem. I've only seen infinite loop when sending C with excitation energies ~<
5 MeV per nucleon. But this should never arrive to multifragmentation. It should
go to fermi breakup.

Even if I've put some protection in multifragmentation to avoid that infinite
loop, you should be careful with the models you use. I think excitation handler
is released with multifragmentation and fermi breakup switched off. If you have
switched multifragmentation on I've no see any reason to do the same in fermi
breakup (in fact fermi is much more tested than multifragmentation).

My advice is to not use multifragmentation by now. I needs some development,
fixing and more testing.

Vicente
Comment 3 Vicente.Lara 2003-10-21 13:17:59 CEST
*** Bug 546 has been marked as a duplicate of this bug. ***
*** 'Vicente.Lara@cern.ch' will be responsible for bug 546. ***
Comment 4 Vicente.Lara 2003-10-21 13:17:59 CEST
*** Bug 546 has been marked as a duplicate of this bug. ***
*** 'Vicente.Lara@cern.ch' will be responsible for bug 546. ***