Project

General

Profile

Minos CS Liaison

The Minos CS Liaison is a person in the Computing Sector.
Their primary responsibility is communication between the CS and the Minos Experiment.
The corresponding role in the Minos Experiment is held by the Online and Offline coordinators.

The effort level is not to exceed 4 hours/week, and should usually be closer to 2.

Work beyond communications, such as investigating and addressing problems, and actively managing the resources, falls to the Offline and Online coordinators and the Collaboration in general.

There is a CSL Fermipoint site https://fermipoint.fnal.gov/organization/cs/scd/sitepages/cs%20liaison%20meetings.aspx
The list of Liaisons, Spokes and Coordinators is at https://fermipoint.fnal.gov/organization/cs/scd/Lists/Experiment%20and%20Scientific%20Collaboration%20Liaison%20Li/AllItems.aspx

Expected Liaison activities :

  • Be subscribed to mailing lists
    • - meeting and service announcements
      • forward service items to Minos as appropriate
    • - service announcements which will be forwarded to cs-liaison
    • gp-downtime - service announcements
      • forward to Minos as appropriate
    • weekly ServiceNow open ticket report
      • Review these for malingerers, poke them as needed ( about 10 minutes/week )
    • minos_batch - most computing operations issues are discussed here, including weekly batch/core meeting announcements
    • minos_software_discussion - former home of code development discussions, mostly merged into minos_batch past 2014
    • minos-admin - system level planning
  • Review open Minos ServiceNow tickets as reported in a weekly email from ServiceNow
  • future - may need to attend weekly All Experimenter Meeting, were an offline computing will be presented starting around Fall 2016.
  • Attend bi-weekly CS Liaison meetings
  • Attend bi-weekly FIFE meetings when Liaisons are invited
  • Attend certain Minos meetings :
    • Minos All Analysis Meeting - Monday 09:00 - the first 1/2 hour where global issues are discussed
    • Detector Operations joint meeting - Monday 09:30 - about 1/2 hour, report on Computing issues including coordination with Minerva
    • Batch/Offline Core Computing Meeting - Thursdays 11:00 - Give the Infrastructure report
  • Annual SC/PMT resource request
    • This is prepared and presented by the Offline and Online Coordinators.
    • Liaison should review and assist with the preparation, to align this with CS plans
    • Attend the annual SC/PMT meeting where this is presented