Membership in LArSoft Collaboration

Once an experiment chooses to be a member of the LArSoft Collaboration, they are expected to:

  1. State explicit support from spokespeople for LArSoft on behalf of the experiment. This includes spokesperson representation in the Steering Group. The steering group includes the spokespeople of the experiments, as well as representatives from Fermilab’s Scientific Computing and Neutrino Divisions. The Steering Group has the authority and the responsibility to make policy decisions and set the overall direction for the Collaboration.
  2. Provide a point of contact within offline software management who is responsible for:
    • ensuring responses on behalf of the experiment to software sign-off requests
    • providing approvals and other input as needed at the LArSoft Coordination Meetings and via email
    • attending Offline Leads meetings and contributing to Offline Leads reports
      • Offline Leads meetings are to review and revise status and changes to the implementation goals of the collaboration including capabilities, milestones and priorities. Discussion at these meetings include direction and priority among the various projects, technical issues that affect multiple experiments, policy issues that may arise from time to time, etc. The outcomes of this group are presented to the Steering Group for endorsement.
  3. Provide a ‘getting started’ page on the experiment website.
    • This page includes the instructions needed for a new user to properly set up the combined experiment and LArSoft offline software environments, procedures for checking out and developing experiment code, pointers to the relevant sections of the LArSoft documentation for items related to how to use, modify and contribute to LArSoft, etc.
    • LArSoft maintains a link to this page on their Quick Links page.
  4. Agree to adhere to the design principles and coding guidelines, and to follow the code submission procedures, including requesting review and approval at the LArSoft Coordination Meeting for code changes authored by the experiment.
  5. Provide as experiment-owned software, the minimum needed to run LArSoft for a new detector, which includes:
    • Defining the geometry for the new detector in a GDML file
    • Customizing E-feld, drift velocity, readout parameters, etc, as needed
    • Customizing digitization for simulation, as needed