Quantum Annealing for stop paper

Dear journal, we would like to thank the referee for this second iteration of comments, as these have further helped us to improve the quality of the paper. All text comments have been addressed in the latest version uploaded (v3). Below, we address the physics comments which need action.

DONE Q1 Indeed, the classification performance is clearly the most important algorithm metric to quantify. The fact that the BDT performs better than a DNN is interesting, and not entirely surprising. Nonetheless, I think giving the reader some indication of the time to solution for the quantum algorithm is extremely important as it clarifies the current practicality and limitations (which may improve dramatically in the near future).

The time to solution is typically the one of the annealing, i.e. 20 micro-seconds. A sentence has been added to cover this point in section 4, at line 230 of the latest version (v3).

DONE Q2 These details of the BDT training should be added to the manuscript, potentially in an appendix if the authors prefer.

According to the previous suggestion of the referee, the details of the BDT training are already in the manuscript: we kindly refer the referee to the appendix A, lines 459-484 of v2 for the details covering both the BDT internal parameters as well as the procedure for finding the best set of input variables to the BDT. These can be found in the lines 464-489 of v3.

DONE Q3 "Indeed: in order to make the comparison with the results of quantum annealing as valid as possible, a BDT was re-trained with the the Delphes simulation. It has to be noted that the performance of the BDT (for the same signal) is compatible between this new simulation and the full simulation of the CMS detector." Could this statement be added to the paper?

This has been added at the end of Appendix A where both the question of simulated samples and the details of the BDT are covered.

DONE Q4 L403: Should this be “comparable to the best-known classical ML tool.” ?

That is indeed a better formulation. The text has been modified as suggested by the referee.

Stop1 direct search at 8 TeV

8 TeV stop studies can be found here

Replies to JHEP's referee can be found here

Stop1 grid

This can be found here

SW guide

This can be found here

Old Jet and MET studies

Some Jet and MET studies can be found here

Old triggers studies studies

trigger studies

-- PedrameBargassa - 28 Jan 2009

Topic attachments
ISorted ascending Attachment History Action Size Date Who Comment
GIFgif cumulativehltrate.1e31.gif r1 manage 25.5 K 2009-05-27 - 22:42 PedrameBargassa Cumulative, per sector rates
GIFgif ele10sumhtscanthreshold.1E31.gif r1 manage 12.6 K 2009-05-21 - 12:17 PedrameBargassa Rate variation versus HT and Jet-input threshold for Ele10_HT
GIFgif mu5sumhtscanthreshold.1E31.gif r1 manage 11.4 K 2009-05-21 - 12:18 PedrameBargassa Rate variation versus HT and Jet-input threshold for Mu5_HT
GIFgif sumhtscanthreshold.1E31.gif r1 manage 11.9 K 2009-05-21 - 12:19 PedrameBargassa Rate variation versus HT and Jet-input threshold for HT
PNGpng LM_Parallel_Coor_Back.png r1 manage 79.6 K 2013-01-16 - 17:33 PedrameBargassa LM ttbar VarCorr
PNGpng LM_Parallel_Coor_Sig.png r1 manage 87.2 K 2013-01-16 - 17:35 PedrameBargassa LM sig VarCorr
PNGpng MVA_4j_antiiso_El.png r1 manage 26.6 K 2012-11-08 - 20:49 PedrameBargassa Single-electron MVA(LM) with RelIso>0.3
PNGpng MVA_4j_antiiso_Mu.png r1 manage 25.9 K 2012-11-08 - 20:50 PedrameBargassa Single-muon MVA(LM) with RelIso>0.3
Edit | Attach | Watch | Print version | History: r147 < r146 < r145 < r144 < r143 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r147 - 2021-08-25 - PedrameBargassa
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback