You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The energy measured in a detector is the integral over the entire G4 event even if two hits are microseconds apart. However, a while back Chen indicated (the first line after "Dear Peter") that he can integrate the energy over small hit windows instead of event windows. So the code may already have the capability to do this.
The text was updated successfully, but these errors were encountered:
So I'm having a quick look into the code now and we have two output variables for energy deposits:
edep: which is the ionising energy deposit (set here), and
edepAll: which is the total energy deposit and uses the GetTotalEnergyDeposit that is mentioned in John's link above (see here and here)
There is also the timing resolution option (tres) in the output configure file (here) which is used here to decide whether the new hit should be separate or merged into the previous one.
So I think we can do have the capability to do this.
Andy's understanding is correct!
edep and edepAll are actually always the same. I left them both available for output just for occasional checking.
The measure window mentioned by John is the so called timing resolution option (tres) mentioned by Andy. I used to set it to 10ns for previous simulation. We should change it according to detector response.
The energy measured in a detector is the integral over the entire G4 event even if two hits are microseconds apart. However, a while back Chen indicated (the first line after "Dear Peter") that he can integrate the energy over small hit windows instead of event windows. So the code may already have the capability to do this.
The text was updated successfully, but these errors were encountered: