|Message: Biasing by physics process||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I want to bias events by physics process, by increasing the cross-section of a given process by name, optionally limited by particle, material, and volume names. G4VProcess has SetPILfactor() which seems specifically designed for this. Unfortunately, it does not affect the track weights.
Adjusting the weights requires the current interaction length for all processes affecting this particle. Fortunately, a quick test program shows that it is available (!= -1) for all processes of interest (processes like msc, Transportation, and step limiters don't matter).
In order to adjust the track weights, between detector construction and beamOn I will loop over all particles' process managers, inserting a process wrapper around all appropriate processes. This will not handle continuous processes properly, so I'll check and fail for them. The wrapper will adjust the interaction length, and adjust the weights of the particle being tracked and all secondaries. The wrapper must do *condition=Forced in the GPIL functions so it can adjust the weight at each step.
Any comments on this? Has anyone done this already?
|Inline Depth:||Outline Depth:||Add message:|