-
Notifications
You must be signed in to change notification settings - Fork 2
T4 and pT4 Creation Draft PR #151
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
T4 and pT4 Creation Draft PR #151
Conversation
|
I can't see at first glance any mistakes. What I would suggest is to make the same plots showing for abs(eta_1) < 1.1 or some value in the barrel the distribution of inner radii / outer radii from the actual features vector only. So to make the plot directly from "features" in the cell below this and see if you still have good separation between real/fake. You could also remove the eta requirement and make the same plot for comparison. The DNN right now is claiming it doesn't see a use of the eta_1 feature (and nearly all of the other hit-based features), so I think that would help clarify where the issue is. You could also remake the same plot after downsampling/etc. as a second check. |
|
Or, retrain with just eta_1 and the radii variables and see if eta_1 is used by the DNN then. That would also help clarify things. |
|
Like I said on the skype chat, if you look at your feature importances Nearly all of your features have ~0 importance or <0 importance. If you look at the T5 DNN feature importances: Or the T3 DNN importances: most features are used. In both cases eta_1 (first eta value, feature 0) is the third most important feature. So I think narrowing the search there will help solve this. |
| constexpr int p08_occupancy_matrix[4][4] = { | ||
| {5000, 5000, 5000, 5000}, // category 0 | ||
| {5000, 5000, 5000, 5000}, // category 1 | ||
| {5000, 5000, 5000, 5000}, // category 2 | ||
| {5000, 5000, 5000, 5000} // category 3 | ||
| }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect the results shown today were truncated in some cases.
I suggest to merge #148 to moderate the memory blowup and increase the above by x10 and redo the inclusive T3 input test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You will need to add similar logic to the Quadruplet occupancy kernel here if you want to increase these 10x btw, since I only incorporated it into the existing objects. Should be only a few lines though that you need to add. See my change for the T5 occupancies as a reference.
b6fc621 to
722178e
Compare
Creation of the quadruplet (T4) and pixelQuadruplet (pT4) objects. T4s are built from two T3s that share a common LS. T4s and pT4s are added as additional objects to track candidates, so the final TC collection includes (in order): pT5, pT4, pT3, T5, T4, pLS. T4s and pT4s can be enabled with compile time flags -t and -T (if only using the pT4 flag, T4s will be built but not included in TCs). Both objects use a DNN for fake rejection. The T4 DNN uses a multi-class architecture (similar to the T3 DNN) which classifies T4s as fake, real prompt, and real displaced. The pT4 DNN uses a binary classification architecture (similar to the T5 and pT3 DNNs).