Problem 2592 - radioactivedecay biasing
Summary: radioactivedecay biasing
Status: ASSIGNED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic/models/radioactive_decay (show other problems)
Version: 11.2
Hardware: All All
: P4 minor
Assignee: Vladimir.Ivantchenko
URL:
Depends on:
Blocks:
 
Reported: 2024-02-05 14:27 CET by michel.maire
Modified: 2024-05-04 15:09 CEST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description michel.maire 2024-02-05 14:27:41 CET
after merge request 4186 (eg. radioactive_decay-V11-02-00) the macro rdecay01/TimeWindowBiased.mac is not working well. The final ion is not created; histogram 8 is empty.
Comment 1 michel.maire 2024-02-25 19:06:44 CET
HI Dennis and All,

 Please compare printout of 11.0 and 11.2

 Final ion, here Ti47, is not created. Then rdecay01 cannot identify the end of decay chain (lines 137 and 180 of TrackingAction), hence not compute the statistic of the event.
 I suspect the origin of this fact is in radioactive_decay-V11-02-00 (MR 4186).

 Dennis, I remember that, once in the past (when ?), we had this problem (eg. final ion not created) that you were able to restaure !
Comment 2 alexander.howard 2024-03-04 15:44:59 CET
(In reply to michel.maire from comment #0)
> after merge request 4186 (eg. radioactive_decay-V11-02-00) the macro
> rdecay01/TimeWindowBiased.mac is not working well. The final ion is not
> created; histogram 8 is empty.

The problem is not related to MR 4186 - this simply protected creating metastable states with infinite lifetime (i.e. stable) due to the zero energy level transitions which should be handled by the upcoming "floating" implementation. I think the issue with the empty histogram 8 occurred 
directly after the beta release of last year, so some months before the release v11.2.
Comment 3 michel.maire 2024-05-04 15:09:43 CEST
remove the command rdm/BRbias from TimeWindowBiased.mac; the biasing of decay time becomes visible again.
But weight of an event is always 1. See trackingAction, lines 184-185; and histo 8