Mandate for HDBS analysis contacts

The duration of the analysis contact appointment usually extends until a paper publication of the analysis. The role as analysis contact has a number of components:

Analysis Planning

• The majority of HDBS analysis teams are currently preparing results using the full Run 2 dataset. Think about what limits the sensitivity across the entire search range with ~140 fb-1 data and consider the broader, and long-term picture as well as the short-term goals:
  • At what luminosity does the analysis become systematically limited?
  • Synergy and harmonization with other analyses (are there areas where tasks can be shared to enable teams to work more efficiently?).
  • Person-power situation for general tasks that are relevant for this analysis
  • Ensure adequate preparation of the statistical analysis and potential combinations with other channels
  • Special requirements from CP groups: minimal requirements for pre-recommendations you plan to use?
  • Special requirements on computing or resources?
  • Special requirements on trigger for Run 3?

Leading an analysis team

• Organize the analysis team, run working meetings as necessary. In general, make sure that all aspects of the analysis are covered and being worked on actively by members of the team. This includes making sure that there is an understanding of the scope of the analysis and a clear agreement of the role of each member of the analysis team.
• Create or update a short and simple TWiki page that contains the basic information about the analysis (mailing list(s), name(s) of contact(s), link to analysis code etc) and make sure the subgroup TWiki page has a link to it.
• Set up an area in git where code used in the analysis is stored (coordinate with subgroup conveners). This git directory will be part of the Glance record for the analysis. The git area for documentation is created via the glance interface.
• Be prepared for a time consuming commitment that could take a large fraction of your time (e.g. working through the weekend to meet deadlines). Presence at CERN is beneficial but not required.
• Inform the HDBS and subgroup conveners if you are unable to fulfill the above tasks because of holidays, sickness, etc.

Interact with CP groups, other physics groups, etc.

• Interactions with your subgroup:
  • Attend all subgroup meetings to stay informed of recent developments in the subgroup and participate in activities of the subgroup.
  • Report the status of the analysis to the subgroup conveners and regularly at subgroup or HDBS meetings. However, it is a good idea to ask different analysis team members to give some of the status report talks at those meetings.

• Interactions with other physics groups:
  • Be informed of the status of your derivation and either be the liaison, or find someone within the analysis team, who can help maintain the derivation, submit requests for derivation production, and prevent deletion of your dataset
  • No HDBS derivations exist (yet) and currently all analyses use derivations from other groups (mostly Exotics and Higgs). This may change in the future if there is a need.
  • Please contact the relevant derivation contact for questions and also tell them when you analysis no longer needs the derivation.

• Interactions with trigger and combined performance groups:
  • Make sure the analysis choices are endorsed by experts. You may also need to enlist their help to provide corrections/smearing to apply to the MC simulation, as required by the analysis. We recommend using harmonized CP objects unless you have good reasons to deviate.
  • The list of HDBS group CP and trigger liaisons can be found on the main HDBS page.
  • Make sure that the strategy of background and systematic uncertainty estimation, MC reweighting/correction procedure uses the prescriptions recommended by PMG (if available) and is discussed in the subgroup.

Preparing for a publication:

• Make sure that all the details of the analysis are well documented in a clear supporting note which will be circulated to the group before the analysis approval and will be turned to an ATLAS INT note once the paper is published.
• Be aware of the approval procedure and help the analysis along the path described in the HDBS Approval Steps TWiki.
• Facilitate the writing of the paper by the paper editors (to be assigned at a later stage - unless the analysis team is very small, the contact and editor should not be the same person).
  • Useful information (including bibtex for common references and text snippets for e.g. MC generators) is found on the PubCom TWiki including the PubComLaTeXDiff.
• Organize meetings and interact with the Editorial Board (once assigned).

Contact HDBS conveners in case of doubt or trouble.

-- KatharineLeney - 2019-01-31