StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18934601
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-21T15:53:36.190
FavoriteCount
0
LastActivityDate
2013-09-21T15:53:36.190
LastEditDate
LastEditorUserId
0
OwnerUserId
2802403
ParentId
6244336
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I finally found an effective solution to that problem: I search for a nucleus in the secondary track vector of a step ending by a neutron capture. This nucleus is the one which captured the neutron and which recoil is tracked by Geant4. Do not forget to subtract 1 neutron to this nucleus to get what you want (for a capture on hydrogen, you will get deuterium with this method). So in my SteppingAction, I add: <pre><code>// neutron capture if ( aStep->GetPostStepPoint()->GetProcessDefinedStep() && aStep->GetPostStepPoint()->GetProcessDefinedStep()->GetProcessType() == fHadronic // see G4ProcessType.hh && aStep->GetPostStepPoint()->GetProcessDefinedStep()->GetProcessSubType() == fCapture // see G4HadronicProcessType.hh ) { if ( aStep->GetSecondary() != 0 && aStep->GetSecondary()->size() != 0 ) { std::vector<G4Track*>::const_iterator it; for (it=aStep->GetSecondary()->begin(); it!=aStep->GetSecondary()->end(); it++) { if ( !(*it)->GetCreatorProcess() || (*it)->GetCreatorProcess()->GetProcessSubType() != fCapture // see G4HadronicProcessType.hh || (*it)->GetCreatorProcess()->GetProcessType() != fHadronic // see G4ProcessType.hh || !(*it)->GetDynamicParticle() || (*it)->GetDynamicParticle()->GetParticleDefinition()->GetAtomicNumber() == 0 // keep only nucleus || (*it)->GetDynamicParticle()->GetParticleDefinition() == G4Neutron::NeutronDefinition() // but not the neutron (perhaps antiparticles could also be checked) ) { continue; } myEventAction->TreatNeutronCapture(*it); break; } if (it == aStep->GetSecondary()->end()) { G4cerr << "\n#### END OF SECONDARY VECTOR REACHED AFTER NEUTRON CAPTURE ! ###\n"; myEventAction->TreatNeutronCapture(0); } } else { myEventAction->TreatNeutronCapture(0); } } </code></pre> As you can see, I defer the actual stepping treatment to methods of EventAction. This is my TreatNeutronCapture method : <pre><code>void MyExperimentEventAction::TreatNeutronCapture(const G4Track* track) { myParticle = myMC->GetParticle(ParticleMap[track->GetParentID()]); if (track == 0) { myParticle->SetFinalProcess(-1); } // if no nucleus is found in secondaries else { myParticle->SetFinalProcess(track->GetDynamicParticle()->GetPDGcode()); } } </code></pre> myParticle and myMC refers to my own data classes.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFind nucleus involved in nCapture process in Geant4
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmaRR
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFind nucleus involved in nCapture process in Geant4
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COYes I ended up doing the same and checking the secondary particles for the nucleus. It's been about two years, but thanks for posting the solution! I'll have to take a look back at my code, but I think there are some details that can reduce the number of checks needed to find the nucleus. I'll mark your answer as correct.
 singulars
 PostPostId
 PO
 UserUserId
 USuser487100

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.