Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record distinct hits within G4 event #35

Open
jrquirk opened this issue Sep 22, 2014 · 2 comments
Open

Record distinct hits within G4 event #35

jrquirk opened this issue Sep 22, 2014 · 2 comments

Comments

@jrquirk
Copy link

jrquirk commented Sep 22, 2014

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.

@AndrewEdmonds11
Copy link

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.

Is there anything else we should know, Chen?

@wuchen1106
Copy link

Sorry guys! I missed this notification.

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.

I think this is enough meet our current goal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants