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

More FDC issues? #66

Closed
T-Britton opened this issue Sep 11, 2018 · 6 comments
Closed

More FDC issues? #66

T-Britton opened this issue Sep 11, 2018 · 6 comments
Assignees

Comments

@T-Britton
Copy link

This sample included all of Richards flags including:
DCAY 0
LOSS 2
MULS 0
DRAY 0

protons at 4 GeV and 15 deg. look equivalent but at 4 degrees:

image

HDGeant4 missing hits on track

image

very different wirebased trackingFOM

image

without multiple scattering we expect the tracking to overestimate the errors, thus causing a pile-up at a CL at 1, as it does with hdgeant. hdgeant4 does not.

You can get access to all of the reconstruction plots via the sept 11 meeting page, many differences to be seen

@zihlmann
Copy link

At the wirebased fit stage there is a tendency to loose the more downstream hits mostly of package 4.
However at the time based stage some of the hits are recovered in the Geant3 version but not in
the Geant4 version. This indicates that the FDC timing is not the same in geant3 and geant4.
This clearly shows that there is an issue with the wirebased tracking algorithm.
the plot below shows the wirebased fit result and the hits/pseudohits that were used.
Note that all hits in package 4 and most of package 3 are not used anymore. They were at
the candidate stage.
wbg4

The second issue with the geant4 simulation is that quite frequently the event has no FDC hits
at all!!!!

@rjones30
Copy link

rjones30 commented Jan 1, 2019

I traced this issue down to an inconsistency in the way fdc chamber layers were being indexed between the g3 and g4 hits libraries. My tests show that the track reconstruction efficiency for hdgeant4 simulation output is comparable to that from hdgeant, once this fix is in place. Experts should confirm this, but I believe this issue can be closed.
-Richard Jones

@T-Britton
Copy link
Author

Great news! I’ll run 2 sets to compare with master branches this week.

@jrstevenjlab
Copy link

jrstevenjlab commented Jan 1, 2019 via email

@rjones30
Copy link

rjones30 commented Jan 1, 2019 via email

@T-Britton
Copy link
Author

A quick check of the above plots show them to be identical (within statistics). This issue is closed!

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

4 participants