|Message: Re: Bias first, but only first, interaction?||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)|
Hi Jason, Yes, G4BOptnForceFreeFlight is implicitly enabled by the biasing operator G4BOptrForceCollision (implemented in geant4/source/processes/biasing/generic). As said in the readme, the logic of this operator is quite complex. This would be possible to define an other and quite simpler biasing operator, making only the force collision part, if you need to always discard the free flight part. Cheers, Marc On 03/02/2018 00:53, Jason Brodsky wrote: > Hi Marc, > > GB02's Readme says that it uses G4OptnForceFreeFlight, but I don't see > that implemented in the actual code (searching the code for that class > name). Is it implicitly enabled by some other step? > > Thanks, > Jason > > On Fri, Feb 2, 2018, 9:41 AM Jason Brodsky <email@example.com > <mailto:firstname.lastname@example.org>> wrote: > > Hi Marc, > > That sounds just like what I'm looking for. I was looking to do > the forced interaction at a given point, but I can of course just > define a small volume and do it that way. Killing the split copy > should be straightfoward; I'll let you know if I can't figure out > how to identify it. > > Thanks, > Jason > > > > On Fri, Feb 2, 2018 at 8:32 AM, Marc Verderi <email@example.com > <mailto:firstname.lastname@example.org>> wrote: > > > *** Discussion title: Biasing and Scoring > > Hi Jason, > > Sorry for the slow answer. > > When you say you want to force the interaction at a given > location, is > this at a given point or inside a given volume ? > > If this is inside a given volume, > examples/extended/biasing/GB02 should > give you something rather close to what you need. This example > implements a forced collision in a scheme similar to the MCNP > one : when > the track enters the volume, one copy is made and is having an > interaction forced inside the volume, an other copy is done, > flying > though the volume without interaction. In your case I > understand you are > not interested in this second copy. If so, we may iterate to > see how to > deal with that (the simplest solution would be to kill this second > copy). > > Cheers, > Marc > > ------------------------------------------------------------- > Visit this GEANT4 at hypernews.slac.stanford.edu > <http://hypernews.slac.stanford.edu> message (to reply or > unsubscribe) at: > http://hypernews.slac.stanford.edu/HyperNews/geant4/get/biasing_scoring/248/1.html > > [ MIME part of type text/html without a name stripped ]