|Message: secondary particle information via hit?||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)|
Hello I'd like to connect information about secondary particles - if created in a hit - to this hit. Yet, what I found is the direct way from "SteppingManager" to "SteppingVerbose", one can access "(*fSecondary)" and "fN2ndaries*DoIt". I do not want to go via SteppingVerbose, anyway I do not know how I could shift this information in SteppingVerbose into step or hit or anything else. How do I retrieve secondary particle information for a hit that I can handle their statistics (name/numbers) via hitscollection event by event? Any ideas are welcome, Edwina Wolff some information I can do connect with hit: ------------------------------------------- edep=step->GetTotalEnergyDeposit(); sensitiveDetectorHit->SetEdep(edep); processName=step->GetPostStepPoint()->GetProcessDefinedStep()->GetProcessName(); sensitiveDetectorHit->SetProcessName(processName); particleName=step->GetTrack()->GetDefinition()->GetParticleName(); sensitiveDetectorHit->SetParticleName(particleName); //this is the currently tracked particle which run the process now I like to do something like: --------------------------------- secondaries=step->GetSecondary; or secondaries=(*fSecondary); sensitiveDetectorHit->SetSecondary( (*fSecondary) ); //to store information about the created secondaries of this hit //(*fSecondary) in SteppingVerbose directly accessable via SteppingManager secondaryName[i]=(*fSecondary)[i]->GetDefinition()->GetParticleName();
|Inline Depth:||Outline Depth:||Add message:|