Detector Performance notes (DP) and Detector Performance Summaries (DPS)

The purpose of Detector performance notes and summaries is the fast dissemination of Detector performance results, mostly for conferences. DP(S) are produced as a conclusion of the internal approval process, and differ in that DP notes remain internal to CMS while DPS are made public, available on CDS, and therefore suitable as reference in proceedings.

A technical details which sometimes confuses people: initially always a DP is submitted, it is elevated to DPS via the procedure explained at the end of the "Approval" section.

While primarily designed for Detector Performance plots from DPGs via Run Coordination , these notes are also used to a lesser extend to disseminate Object Performance plots form POGs via PPD , in the absence of corresponding PAS or short-term publication, and for Detector Performance Plots for Upgrade via UPSG.

Approval process

The main purpose is to approve plots, and to make them available for speakers. The approved material is therefore a set of slides regrouping plots and the minimal information mandatory to understand them. A twiki must also be prepared. There are 4 mandatory steps :

Pre-approval

Results must be pre-approved within the corresponding DPG or POG or UPSG group (Note from Gaelle - UPSG is acting like RC or PPD, plots should be first pre-approved in the DPG and POG *beforehand . It is of the responsibility of the group to scrutinize the validity of the material being presented from a physics and technical point of view. The style of figures must also be checked against the basic CMS style guidelines reminded below.

Plots in a DP or DPS must meet the quality standards set by CMS for all scientific publications. In addition, since they are intended to be included in conference talks, they must be as explicit as possible. In particular, acronyms and jargon must be avoided. In rare case, the accompanying text may provide necessary information, but keep in mind that most often the plot will be presented without that text.

Note on Style of plots

Plots in a DP or DPS must meet the quality standards set by CMS for all scientific publications. The figures should follow the style suggestions given here. Please use the macro http://cmsdoc.cern.ch/cms/cpt/tdr/tdrstyle.C when possible. If plots are prepared with another tool than ROOT, the author must reproduce that style as accurately as possible.

• Figures should mention "CMS Preliminary".
  • "CMS Simulation Preliminary "
  • "CMS Preliminary, sqrt(s)= 8TeV" for 2012 data and "CMS Preliminary, 2011 data at sqrt(s)= 7TeV " or "CMS Preliminary, 2010 data at sqrt(s)= 7TeV" for 2011 and 2010 data respectively
  • In general only specify the date when there is an ambiguity: 1) when the result depends on when the data has been analyzed. For instance if a plot is produced with a calibration or an alignement, or a new algorithm, that were only available in 2014, then use "CMS Preliminary 2014" to make the point. 2) when the result depends on which data has been analyzed. For instance if there are periods with different data taking conditions: "2010 data at 7 TeV" is not the same as "2011 data at 7 TeV".
• Where appropriate, figures should indicate the integrated luminosity.
• %COLOR%For the so-called Ultra Legacy Run2 reprocessing results , plots should be labeled as “Run-2 Legacy” (no mention of Ultra which is CMS internal jargon)

• Fonts
  • Large for readability
  • Standard fonts : Arial, Times New Roman, or similar
  • Do not use Comic Sans MS
• Label Axes and units must be present. CMS prefers natural units.
• Plot Captions:
  • In a separate text box, include a very succinct summary of the key info

Event displays:

• Include 2 copies of each display – one with dark and one with light background
• Include the standard label (from fireworks or similar):
  • CMS Experiment at the LHC, CERN
  • Date Recorded
  • Run/Event
• Fonts (same as for plots)
  • Large for readability
  • Standard fonts : Arial, Times New Roman, or similar
  • Do not use Comic Sans MS
• Include information regarding the displays in a separate text box or separate slide.

Approval

The proposal of material for approval should come from the DPG/POG/UPSG conveners. (Note from Gaelle : no the UPSG has the role of RC and PPD note the role of DPG and POG) They are co-responsible for the approval and should therefore follow the meeting when not presenting themselves.

The approval takes place at a general meeting. Either the PPD general meeting (mostly for POGs) or the Run Organization meeting (primarily for DPGs) or the UPSG (for Phase 2 Upgrade physics plots and Phase 2 related DPG/POG developments). The material, in a twiki form, should be posted on commissioning hn for DPGs and on physics validation hn for POGs at least two days before the approval meeting. For Phase 2 related DPG/POG DPSs, and UPSG physics plots, the material (Twiki and slides) should be added and linked to a weekly UPSG meeting agenda and explicitly announced on the UPSG hn two days prior to approval. The DPS subeditors, acting on behalf of Upgrade, DPG coordination and Physics coordination, check that the style guidelines above are followed, and otherwise ask for the plots to be corrected prior to the meeting.

During the approval session, results are scrutinized both on the content and on the style. Plots may be approved, rejected, or may receive comments on the style to be implemented before the next step.

At this stage, figures that obviously do not follow the guidelines set above will be rejected without any discussion.

*When approving what has to become a DPS (public), the subeditor will need to put in the Comments field "Public DPS TO CDS" to be explicit about the status of the material. This is the step which differentiates DP (internal) and DPS (public).*(Comment from GB : note ta the right place

Collaboration-wide advertisement

The set of slides incorporating the comments received during the approval meeting are posted on the Weekly General Meeting (WGM) agenda for information and comments. If no comment is received within 48h, the plots are considered public and can be shown at conferences/seminars. If comments are received they should be implemented after informing and getting consensus from the Run Coordination or PPD conveners or UPSG conveners. An explicit email replying to the original hn request confirms the final approval. Soon after (within a week), the approved plots must appear on a page linked on the CMS Physics Results web page (currently not available for Upgrade, stay tuned), and a DP or DPS must be created on iCMS.

Creation of the DP or DPS on iCMS

DP and DPS must be created on iCMS as a "Performance Note". These documents are created directly from the slides presented for approval, and will include no modification with respect to the version uploaded to the CWR agenda the week before (apart from implementation of the comments sent by the collaboration) For DP one contact person/email is provided either for the document, or on a per plot basis. The author field in iCMS should always be filled (for DPS and DP) as CMS Collaboration.

For DPS, since these are public CMS documents, there will be no reference to internal material, and only approved plots will be included. DPS are signed by the CMS collaboration and only generic email addressed are allowed as contact (ex cms-dpg-conveners-X at cern.ch) Additional material may be included but should be kept at the minimum and only give the necessary information to understand the plots. As for other publications, the inclusion of already approved results is discouraged and should always come together with the corresponding reference.

Up to four files can be uploaded when creating the note. A blank placeholder must be inserted when adequate:

• Public PDF file : The presence of that file defines a DPS. Only the public PDF will be uploaded to CDS. If not present, the note will be considered as a DP and will remain internal. While plots in a DP note are approved for conferences, there is no way to refer to a DP note in proceedings, and it will be difficult/impossible for non-CMS speakers to use them. Note that even if you want to have only a DP, a dummy empty file must still be submitted as public.
• Public PPT file : If present, the public PPT will be publicly accessible via iCMS. The content must be identical to the public PDF. The purpose is to help speakers in the preparation of their talk by enabling them to easily grab the original high-definition plots.
• Private PDF file : This is the main document in the case of a DP note. For DPS, this is the opportunity to provide additional background material to CMS speakers. The file can only be accessed after authentication on iCMS.
• Private PPT file: see above. The file can only be accessed after authentication on iCMS.

Review Status

GaelleBoudoul - 2019-03-18

-- GaelleBoudoul - 2020-04-06