- Compact style
- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
https://tinyurl.com/T1-GGUS-Open
https://tinyurl.com/T1-GGUS-Closed
https://lcgwww.gridpp.rl.ac.uk/utils/availchart/
https://cms-site-readiness.web.cern.ch/cms-site-readiness/SiteReadiness/HTML/SiteReadinessReport.html#T1_UK_RAL
http://hammercloud.cern.ch/hc/app/atlas/siteoverview/?site=RAL-LCG2&startTime=2020-01-29&endTime=2020-02-06&templateType=isGolden
* ATLAS needs to run more single-core analysis jobs
- https://helpdesk.gridpp.rl.ac.uk/Ticket/Display.html?id=397775
* ATLAS hostname env for WN containers
- https://helpdesk.gridpp.rl.ac.uk/Ticket/Display.html?id=398494
* Oxford Xcache; Done on RAL side
- https://helpdesk.gridpp.rl.ac.uk/Ticket/Display.html?id=397191
Discrepancy between Vande 100% CPU (for ATLAS) and ATLAS Monitoring (cf. Vande * 11.7/10).
- to be understood
ATLAS slowly increasing Single-core running jobs (to ~ 3k).
Vector Reads:
CMS Sam test code can run on gw683 and gw691:
- See at what frequency problem can be triggered;
- In parallel try some lower-level tests
SAM tests are ok, just occasional failures. Transfers seem fine.
However, real jobs are failing at a very high rate. Efficiency is extremely low. CMS L1s have asked me to organise stopping Processing-type jobs running at RAL, as these are the culprits. Failures are 60-80% and efficiencies are <1% for many jobs. These jobs mostly fail with FileOpen or File Read.
I changed the redirector fallback from the UK alias to the European alias. This seemed to reduce the number of FileOpen errors (the total number of failures remained high - FileOpen errors were replaced by FileRead errors).