-
Notifications
You must be signed in to change notification settings - Fork 9
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
labels filling correctly? #35
Comments
Why doesn't this happen every time? Example of correct label:
What's in the ROOT file:
|
Oh shit! The Run,subrun,event numbers are different... Something is not right ... I checked I am filling from same file I am checking with ROOT... |
some notes: use_thread = false, non-random: seems ok. it says it is processing entry X, and the ROI dumped out matches. use_thread = true, non-random: seems ok use_thread = true; random: weirdness use_thread = false; random: weirdness i'm relying on cout with threads -- dangerous? but it is single thread filling sequentially? |
there a double-shuffle? In initializer of https://github.com/LArbys/LArCV/blob/master/core/Processor/ProcessDriver.cxx In https://github.com/LArbys/LArCV/blob/master/app/APICaffe/ThreadDatumFiller.cxx the entry to be drawn is randomized between (0,numentries in tree) But when it goes to process driver, this X is used to get entry Y = _access_entry_v[X]. X is stored in vector passed back to analysis. So when training, correct label for an image is sent to net. but the wrong entry number for image-ROI pair is passed back to analysis script. |
Fixed in #36 |
From the Filler:
Looking into the ROOT file:
Labeled as cosmic, but definitely a neutrino image.
—— the code ——
Diagnosis
In the loop, the first entry it sees is a cosmic ROI.
It then breaks, missing the MC ROIs behind it. This get's labeled as cosmic, but it's a neutrino.
The text was updated successfully, but these errors were encountered: