| 1 | = Abstract = |
| 2 | |
| 3 | Lines 1 and 2: ”the DELPHES fast-simulation framework is presented” |
| 4 | makes the reader think that the content of the article is purely related to the |
| 5 | software technicalities, while the paper is instead mostly about the physics |
| 6 | content of the fast simulation - if one excepts Section 5. [See related comment |
| 7 | about Section 5 below.] |
| 8 | |
| 9 | Suggestion : Replace ”fast-simulation framework” by ”fast simulation”, |
| 10 | and remove the second sentence, which is out of place in an Abstract. |
| 11 | |
| 12 | Lines 5 to 9: The description of DELPHES in the abstract is too software |
| 13 | oriented. The journal to which the preprint is submitted is called ”Journal |
| 14 | of High-Energy Physics”, not ”Journal of High-Energy Software”. The ca- |
| 15 | sual reader does not really care that the program produces ”collections”, he |
| 16 | cares instead about the physics content of the simulation. The suggestion |
| 17 | here would be to rephrase the end of the abstract to indicate the simulation |
| 18 | was enhanced with new features, needed for the simulation of the LHC de- |
| 19 | tectors in the coming period (e.g., additional pile-up interactions, which will |
| 20 | become crucial in the coming decade, or particle-flow reconstruction, which |
| 21 | has become a salient feature in the first years of the LHC for one of the two |
| 22 | multi-purpose detectors), and that the program simulates ”physics objects” |
| 23 | used for data analysis at hadron colliders such as ”jets”, ”taus”, ”missing |
| 24 | energy”, ”electrons”, ”muons”, ”photons”, ”isolation”, ”pile-up mitigation”, |
| 25 | etc. |
| 26 | |
| 27 | It is indeed important that the concept of ”hadron collider” appears clearly |
| 28 | in the abstract. Because the simulation is analysis-oriented, it would take a |
| 29 | number of important modifications to make it useable for analysis of e+e- |
| 30 | collisions, for example. |