The LHC EFT Working Group Twiki page

This is the public home page of the LHC Effective Field Theory Working Group. The mandate of the group can be found on the main LPCC EFT WG web page

* Sign up to the general WG mailing list

* Send mail to conveners

Activitiy Areas

The activities of the group are divided into 6 areas. The wiki pages associated with each area are given below:

Working group meetings:

Upcoming Meetings

Past Meetings

  • Dec 7th 2020 at 2pm CERN time: EFT Formalism
  • Dec 14th 2020 at 2pm CERN time: Predictions and Tools
  • Jan 11th 2021 at 2pm CERN time: Measurements and Observables
  • Jan 27th 2021 at 2pm CERN time: Fits and Related Systematics
  • Feb 8th 2021 at 2pm CERN time: Benchmark Scenarios from UV Models
  • April 12th 2021 at 2pm CERN time: Heavy flavour inputs to EFT fits
  • May 3rd 2021 at 2pm CERN time: 2rd General meeting
  • November 22th 2021 at 2pm CERN time: 3rd General meeting
  • May 23rd 2022 at 2pm CERN time: 3rd General meeting


LHC EFT Working Group Category in CDS

Guidelines for preparation of the LHC EFT WG reports

  • A topic is identified as important and/or interesting by either the WG conveners or WG members and is discussed at the WG meeting(s). An expression of interest on a specific topic should be communicated to the WG conveners.

  • The report's idea should be discussed with conveners before starting editorial work on the draft. Authors from the WG write a draft of the report, which is then submitted to conveners in the appropriate Area. Everyone who has substantially contributed to the work and the discussion, as judged by the WG conveners and the authors, is invited to sign the report.

  • Original plots produced for the report may carry a simple LHC EFT WG logo. Every figure or piece of numerical information coming from an LHC experiment meant to be used or shown in a public document, during a workshop, or in a working group meeting requires a sign-off by the corresponding collaboration before being shown. This continues to apply if only generator information is used but not detector simulation, as long as the MC is used within and with the corresponding setup of the collaboration.

  • The publication committee of the related LHC experiments must be informed and the publication guidelines of the respective collaboration should be followed. The general guidelines from the LHC experiments are expected to be summarized in a common document coordinated with the LPCC. Documents producing new measurements or data combinations should be signed by the full collaboration unless the collaboration decides that the topic is of limited interest and prefers not to submit it to a journal. In other cases, documents can be signed by a limited number of authors if this process follows the publication guidelines of the respective collaborations.

  • Intermediate presentation of the report draft to the WG at WG meetings is encouraged, with an option to provide early comments. These comments may also be requested via email. The completed draft is brought to the attention of the Steering Group (including conveners from all Areas) and is discussed at a Steering Group meeting.

  • WG conveners decide, in coordination with the authors, if the note is appropriate to become an official LHCEFTWG report in the current form, or if it needs to be revised, merged with other work, or reconsidered.

  • If the report is approved by conveners for circulation, a CERN-LPCC report number is requested and a cds entry is created. This automatically creates an LHCEFTWG report number. The front page of the report should clearly state that this is a draft created for comments. The draft report is then advertised in the WG email list and comments are collected on cds for at least one week, which can be adjusted to the complexity of the content, length of the report, and accounting for major holidays. A follow-up email is sent when comments are addressed, and the report is approved by conveners.

  • The approved report should display the LPCC and LHCEFTWG report numbers and include the endorsement “work done on behalf of the LHCEFTWG”. Approved reports can be submitted to arXiv. The documents submitted to arXiv and CDS should both coincide with the version endorsed by the LHCEFTWG. If any part of the work presented in the report or otherwise developed within the LHCEFTWG is included in a journal publication, an acknowledgment should refer to the work performed within the LHCEFTWG.

Standardized template for a LHC EFT WG report

Document submission & collection of comments(DRAFT)

When a new document for the LHC EFT WG is ready for review by the whole group, one of the conveners will upload it to CDS via the generic upload interface navigating to "Research and Computing" → "Experimental Physics: LHC" → "LHC Working Group" → "LHC Effective Field Theory Working Group". The record can be marked either as draft or as final. The same interface can be used to modify the record later, e.g. to upload a new version or to change the status from Draft to normal.

CDS will automatically generate an identifier for the document in the form CERN-LHCEFTWG-yyyy-nnn. A global CERN-LPCC-yyyy-nnn identifier, as for all LPCC reports, can be obtained by asking Michelangelo Mangano. Both identifiers should be included when the note is later submitted to the arXiv, so that CDS can then link the CDS and ArXiv records.

Comments to the documents can be submitted by any authenticated user from the Discussion tab on the CDS record.

useful links

-- PierreSavard - 2020-11-16

Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2022-10-20 - SandraHorvat
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCPhysics All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2023 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