/AIFriendly-LHC

AI-Friendly learns from LHC data

Primary LanguagePython

AIFriendly-LHC

AI-Friendly learns to detect Higgs' Boson in a dataset with simulations from the Large Hadron Collider


1) What are the features in a Large Hadron Collider database?


The format this work refers to is the LHCO format. It has three types of features: kinematic, particle numbers (e.g. leptonic number) and others (dummy features and event index). In the present work we will refer to the presence or absence of the particle numbers by refering to the 'full' database VS the 'kinematic' database.

2) What is AI-Friendly's performance over the database?


When trained over the full database (i.e. the database with both kinematic info and particle numbers info) AI-Friendly obtained a classification accuracy of more than 80% which led to a model with an area under the reciever operating curve (ROC) of more than 90% (see graph below).


Full Database.
LEFT: training metrics (loss and accuracy) for the training and validation set; MIDDLE: ROC-curve over the testing set; RIGHT: output weights per category over the testing set.

3) How important is the kinematic information?


AI-Friendly was trained over the kinematic database (i.e. the database with only kinematic features) and the performance was approximately the same. The conclusion is that kinematic information has a high relative importance


Only Kinematic Information.
LEFT: training metrics (loss and accuracy) for the training and validation set; MIDDLE: ROC-curve over the testing set; RIGHT: output weights per category over the testing set. Compare against the previous chart and note that the AUC and accuracy is almost the same

4) How important is the coordinate system in which the kinematic information is expressed in?


AI-Friendly was trained over the kinematic database rewritten in cartesian coordinates and the predictive quality was relatively poorer than the one obtained from training AI-Friendly with the spherical coordinate system


Only Kinematic Information in cartesian coordinates.
LEFT: training metrics (loss and accuracy) for the training and validation set; MIDDLE: ROC-curve over the testing set; RIGHT: output weights per category over the testing set. Compare against the previous chart and note that the AUC and accuracy is now worst

5) Does adding more layers increase AI-Friendly's accuracy when the coordinate system is cartesian? Why?


Allowing AI-Friendly to perform 'Deep Learning' (i.e. adding two layers) led to better results for the kinematic database in cartesian coordinates and the interpretation is that, as more depth allows for a greater complexity, it is now possible for AI-Friendly to internally map the cartesian vectors into a somewhat more convenient system.


Only Kinematic Information in cartesian coordinates with Deep Learning.
LEFT: training metrics (loss and accuracy) for the training and validation set; MIDDLE: ROC-curve over the testing set; RIGHT: output weights per category over the testing set. Compare against the previous chart and note that the AUC and accuracy is now better. The database wasn't big enough to allow the adding of even more layers.