Fork me on GitHub

Changes between Version 13 and Version 14 of Private/RefereeComments/Section_6


Ignore:
Timestamp:
Oct 16, 2013, 11:28:41 AM (11 years ago)
Author:
Christophe Delaere
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Private/RefereeComments/Section_6

    v13 v14  
    1414comparison with the actual CMS and ATLAS resolutions and granularities.
    1515
    16 >>> The authors disagree with this comment. The reasons are:
    17 
    18 >>>- the resolutions in the Delphes CMS and ATLAS cards are taken directly from the cited papers, and it would be redundant to quote them here.
    19 >>>- the only possible difference is in the calorimeters granularity. Both the CMS and ATLAS configurations in Delphes use the granularity of the HCAL detector. As said in the calorimeter section, the ECAL granularity is exactly the same as the HCAL >>> granularity in Delphes. This comment has now been added.  A table with the actual HCAL granularity of the LHC experiments (already public in the relevant technical design reports of CMS and ATLAS) >>> would be of poor interest to the reader and redundant. 
     16> The authors disagree with this comment. The reasons are:
     17>>(CD) We disagree...
     18>- the resolutions in the Delphes CMS and ATLAS cards are taken directly from the cited papers, and it would be redundant to quote them here.
     19>- the only possible difference is in the calorimeters granularity. Both the CMS and ATLAS configurations in Delphes use the granularity of the HCAL detector. As said in the calorimeter section, the ECAL granularity is exactly the same as the HCAL granularity in Delphes. This comment has now been added.  A table with the actual HCAL granularity of the LHC experiments (already public in the relevant technical design reports of CMS and ATLAS) would be of poor interest to the reader and redundant.
     20>(CD) I think that the text should state the unique version number used for the paper. ATLAS and CMS cards may evolve in the future, and it should be clear to what minor version we refer in the paper.
    2021
    2122PAGE 13
     
    2425
    2526 * It is not clear what the grey bands are in this plot. Shouldn’t they be removed? In CMS, they are supposed to cover differences between the simulation and the data in CMS, not the difference between Delphes and CMS. This comment is valid for all plots. Strangely enough, the ATLAS fred band width is way smaller than that for CMS. Does it represent the same thing ?
    26 >>> the grey bands mean different things in the left and right plots. The caption has been extended in order to explain the details required by the referee.
     27> the grey bands mean different things in the left and right plots. The caption has been extended in order to explain the details required by the referee.
     28>>(CD) it should be said in the caption that the error bars are smaller than the dots. Avoid also to refer to colors.
    2729 * For all plots, it is important to have the statistical uncertainty bars indicated, or to state that they are covered by the size of the markers. In the latter case, an explanation is needed for the apparent scatter of the DELPHES points, and to compare this scatter with the input resolution function.
    28 >>> The apparent scatter is just due to the fact the the parametrisation of the resolution is binned, and has been chosen to match approximately that of CMS and ATLAS. The choice was made to adopt round values which may result in the apparent scatter. As these plots are just an illustration of a parametrisation which is correct by construction, we believe that no further explanation is needed.
     30> The apparent scatter is just due to the fact the the parametrisation of the resolution is binned, and has been chosen to match approximately that of CMS and ATLAS. The choice was made to adopt round values which may result in the apparent scatter. As these plots are just an illustration of a parametrisation which is correct by construction, we believe that no further explanation is needed.
    2931 * For all plots, label, legends, etc... are way too small to be readable.
    30 >>> this comment has been addressed for all the plots.
     32> this comment has been addressed for all the plots.
    3133
    3234
     
    3840core of the CMS resolution, rather than the effective 68% width.
    3941
    40 >>> the referee is correct, the electron resolution was parametrized with the Gaussian width, since the resolution in Delphes is Gaussian by construction. By proceeding this way we are voluntarily neglecting the tails effects in Delphes.   
     42> the referee is correct, the electron resolution was parametrized with the Gaussian width, since the resolution in Delphes is Gaussian by construction. By proceeding this way we are voluntarily neglecting the tails effects in Delphes.   
     43>>(CD) I think that it should be said somewhere in the paper.
    4144
    4245PAGE 14
     
    6063strategy of the expensive LHC detectors).
    6164
    62 >>> addressed. However, the referee, as well as the LHC experiments, should be aware that any study performed with Delphes should be understood as preliminary. A Delphes based study should be perfomed after a pure parton-level and before
    63 >>> a geant based fast or full-simulation study. As a result, the authors are perfectly happy with an agreement with a few percents discrepancy in the physics object resolutions.
     65> addressed. However, the referee, as well as the LHC experiments, should be aware that any study performed with Delphes should be understood as preliminary. A Delphes based study should be perfomed after a pure parton-level and before
     66> a geant based fast or full-simulation study. As a result, the authors are perfectly happy with an agreement with a few percents discrepancy in the physics object resolutions.
     67>>(CD) I would add that "we made this point clear when consulted by the LHC collaborations. Delphes is designed as a
     68>> pheno tool, not as a replacement of fast simulation tools from the collaborations.
    6469
    6570== Section 6.3 ==
     
    7277
    7378>>> addressed. Added a sentence at the beginning of the paragraph stating that only the fake MET is done with pile-up.
    74 
    7579>>> what do we say here?
    7680>>> (michele suggested answer)
    77 
    7881>>> We don't want to create to much imbalance between CMS and ATLAS (the only exception is electrons, but we did not find the relevant plot for ATLAS),
    7982>>> so we have decided to produce a real MET validation plot for CMS and the fake validation for ATLAS. This choice was simply driven by the fact that the real MET
     
    9194Section 7.2)
    9295
    93 >>> "cone" changed to "parameter"
     96> "cone" changed to "parameter"
     97>>(CD) probably not something to say to the referee, but while I fully agree for Kt, anti-Kt jets are still contained in a cone of radius R.
    9498
    9599L9/11: The slight difference of efficiency is a large difference (20%), which
     
    98102prit (jet energy correction or b tagging efficiency should be fixed in DELPHES.
    99103
    100 >>> We totally disagree with the referee here. The examples given here a purely illustrative and it is out of scope
    101 >>> to fine-tune them. The purpose was precisely to show the opposite: without particular fine-tuning
    102 >>> Delphes gives very reasonable agreement with the CMS analysis. We insist that a 20% difference
    103 >>> is an acceptable difference since very often results (rates, efficiencies) obtained with full geant based simulation give larger discrepancies than 20% with respect to data.
    104 >>> As a side comment, the efficiency was re-computed after the change in the energy-flow algorithm and the result was found to be the same.
     104> We totally disagree with the referee here. The examples given here a purely illustrative and it is out of scope
     105> to fine-tune them. The purpose was precisely to show the opposite: without particular fine-tuning
     106> Delphes gives very reasonable agreement with the CMS analysis. We insist that a 20% difference
     107> is an acceptable difference since very often results (rates, efficiencies) obtained with full geant based simulation give larger discrepancies than 20% with respect to data.
     108>>(CD) Add: Most LHC analysis nowadays make use of signal-free regions to normalize backgrounds, and scale factors in excess of 1.2 are not unusual.
     109> As a side comment, the efficiency was re-computed after the change in the energy-flow algorithm and the result was found to be the same.
     110>>(CD) More generally, private communications from CMS collaborations recently confirmed that an excellent agreement is observed when comparing Delphes to internal studies made with full simulation. Unfortunately, these are not results that we are allowed to show.
    105111
    106112Par 2:
     
    200206pile-up produced by LHC in 2012.
    201207
    202 >>> "high pile-up scenarios" has been replaced by "extreme pile-up scenarios", which is we actually meant.
    203 >>> To our knowledge there is no evidence that fast-simulation can cope to >100 simultaneous interactions environments, simply since these did not occur in any hadron collider yet.
     208> "high pile-up scenarios" has been replaced by "extreme pile-up scenarios", which is we actually meant.
     209> To our knowledge there is no evidence that fast-simulation can cope to >100 simultaneous interactions environments, simply since these did not occur in any hadron collider yet.
     210>>(CD) I would reformulate further the sentence in the paper, saying that Delphes has not yet been compared to fullsim at extreme PU. Indeed, once done, it may become more quantitative in that region too. Still, by the time we reach such pileup conditions, experimental collaborations may find ways to cope with pileup that are not foreseen in Delphes.