| 3 | PAGE 12: |
| 4 | |
| 5 | Section 6.1 |
| 6 | Last line: What does ”alternatively” mean ? If one choice is for electrons |
| 7 | and the other for muons, the authors should state it clearly. |
| 8 | |
| 9 | Footnote: this statement deserves a complete section, with the list of |
| 10 | parameters used in the default CMS and ATLAS configurations, as well |
| 11 | as possible explanations as to why this parameter choice was made, and a |
| 12 | comparison with the actual CMS and ATLAS resolutions and granularities. |
| 13 | |
| 14 | PAGE 13 |
| 15 | |
| 16 | Figure 3 |
| 17 | |
| 18 | * It is not clear what the grey bands are in this plot. Shouldn’t they be |
| 19 | removed? In CMS, they are supposed to cover differences between the |
| 20 | simulation and the data in CMS, not the difference between Delphes |
| 21 | and CMS. This comment is valid for all plots |
| 22 | Strangely enough, the ATLAS fred band width is way smaller than that |
| 23 | for CMS. Does it represent the same thing ? |
| 24 | * For all plots, it is important to have the statistical uncertainty bars |
| 25 | indicated, or to state that they are covered by the size of the markers. |
| 26 | In the latter case, an explanation is needed for the apparent scatter |
| 27 | of the DELPHES points, and to compare this scatter with the input |
| 28 | resolution function. |
| 29 | * For all plots, label, legends, etc... are way too small to be readable. |
| 30 | |
| 31 | Figure 4 |
| 32 | |
| 33 | Looking at Ref. [20], and in particular its slide 33, my impression is that |
| 34 | the DELPHES resolution is a factor 2 optimistic with respect to the CMS |
| 35 | resolution. It seems that DELPHES parametrized the Gaussian width of the |
| 36 | core of the CMS resolution, rather than the effective 68% width. |
| 37 | |
| 38 | PAGE 14 |
| 39 | |
| 40 | Figure 5 |
| 41 | |
| 42 | On the CMS side, it would be nice to have an explanation for the following |
| 43 | effects (already alluded to above): |
| 44 | * why does the calo jet resolution curve saturates at low jet pT ? |
| 45 | * why does the PF jet resolution curve of Delphes departs from CMS at high pT? (it’s probably because the tracker pT resolution is used to |
| 46 | determine the PF track pT) And at low pT ? Actually, the DELPHES jet pT resolution is almost independent with pT: it goes from 10 to 7% |
| 47 | when varying the pt from 30 to 500 GeV/c, while the actual CMS PF varies from 14% to 5%. |
| 48 | * why does the PF curve show a discontinuity between the 1st and 2nd points ? |
| 49 | |
| 50 | Once the effects are understood, it would be important to fix the imple- |
| 51 | mentation in DELPHES. These differences are important for data analysis, |
| 52 | and may to DELPHES user draw wrong conclusions from his DELPHES |
| 53 | studies (of particular importance if DELPHES is used to define the upgrade |
| 54 | strategy of the expensive LHC detectors). |
| 55 | |
| 56 | Section 6.3 |
| 57 | |
| 58 | Par 2: |
| 59 | |
| 60 | It is not clear if the CMS study is made with of without pile-up. As pile-up |
| 61 | and its particle-flow mitigation are an important adds-on to DELPHES 3.0, |
| 62 | it would be nice to have an illustration of their performance here. |
| 63 | |
| 64 | PAGE 16 |
| 65 | |
| 66 | Par 1: |
| 67 | |
| 68 | L3: The anti-kT algorithm has no ”cone” - and ”a cone R = 0.5” has |
| 69 | no meaning even for a cone algorithm. (Note: the same mistake occurs in |
| 70 | Section 7.2) |
| 71 | |
| 72 | L9/11: The slight difference of efficiency is a large difference (20%), which |
| 73 | might the DELPHES user draw incorrect conclusions from the abilities of |
| 74 | his/her analysis. The explanation given here should be checked, and the cul- |
| 75 | prit (jet energy correction or b tagging efficiency should be fixed in DELPHES. |
| 76 | |
| 77 | Par 2: |
| 78 | |
| 79 | Bullet 1: ”any parton from the top quark decay” ! ”any parton from the |
| 80 | decay of either of top quarks”. I find the definition of unmatched rather un- |
| 81 | natural. If the three jets from the ”hadronically-decaying top” were matched, |
| 82 | I fail to understand why the event is classified as unmatched, even if the other |
| 83 | b for the other top is unmatched. |
| 84 | |
| 85 | Par 3: |
| 86 | |
| 87 | L5: Why are the distributions not normalized to the number of events ? Is |
| 88 | it because the number of permutations/event is vastly different in DELPHES |
| 89 | and in CMS ? If it is the case, shouldn’t DELPHES be fixed ? |
| 90 | |
| 91 | L9/10: ”Pile-up, not considered in the present study, can degrade the jet |
| 92 | energy resolution.” : A strong emphasis is put on the ability of Delphes 3.0 |
| 93 | to simulate pile up, and to simulate its mitigation procedures based on the |
| 94 | PF reconstruction. Since Delphes is fast, I would assume that it would take |
| 95 | no time to redo this study with pile-up. It is disappointing for the reader not |
| 96 | to see this validation in the paper. It actually casts doubts on the DELPHES |
| 97 | ability to accurately simulate pile-up and its mitigation, which is surely not |
| 98 | what the authors aim at. |
| 99 | |
| 100 | PAGE 17 |
| 101 | |
| 102 | Figure 7 |
| 103 | |
| 104 | The bottom inserts of all plots are difficult to understand. The label ”rel. |
| 105 | diff.” makes the reader guess that they show the relative difference (i.e., |
| 106 | the ratio - 1) of the two distributions, but a quick look at the distributions |
| 107 | leads the reader to doubt about it. For exampe, the right plot shows a 20% |
| 108 | difference between the two distributions around the maximum, which is not |
| 109 | visible in the ”rel. diff.” plot. Maybe the wrong scale was chosen for the |
| 110 | bottom inserts ? |
| 111 | |
| 112 | PAGE 18 |
| 113 | |
| 114 | Par 4: The reader is again disappointed to see that, in the search for VBF- |
| 115 | produced Higgs boson with pile-up, for which it is said that pile-up has a |
| 116 | pretty large and negative impact, the authors decided to use calorimeter jets |
| 117 | instead of particle-flow reconstruction, aimed exactly at mitigating pile-up |
| 118 | effects. Again, it casts doubts on the ability of DELPHES to simulate pile-up |
| 119 | in particle reconstruction, and to simulate its mitigation with particle-flow |
| 120 | reconstruction. The paper has therefore the effect opposite to what the |
| 121 | authors are aiming at. |
| 122 | |
| 123 | Criterion 2. |
| 124 | |
| 125 | The pT cut used to count light jets between j1 and j2 ought to be given. |
| 126 | Are these four cuts used in the CMS analysis which the authors are using for |
| 127 | comparison ? |
| 128 | |
| 129 | PAGE 20 |
| 130 | |
| 131 | Par 2: |
| 132 | |
| 133 | L4: ”accurate productions in high pile-up scenarios should solely rely on |
| 134 | full simulation tools” is very strong, and probably incorrect statement, and |
| 135 | should probably be removed (or seriously rephrased). |
| 136 | |
| 137 | First, it casts again large doubts on the pertaining DELPHES ability to |
| 138 | simulate pile up interactions. |
| 139 | |
| 140 | Second, the fact that, maybe, DELPHES cannot deal with high PU en- |
| 141 | vironment does not mean that other fast simulation tools cannot do. For |
| 142 | example, it seems the CMS fast simulation deals pretty well with the high |
| 143 | pile-up produced by LHC in 2012. |
| 144 | |