In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
Basic concept is to have three half-day sessions for newcomers and oldcomers - both students and more experienced people. Two of the three sessions will be overview talks/discussions; the third is a visit to the P5 site.
Main presenters and discussion leaders should be the CMS Management, Subsystem Managers and Coordinators. Presentations should be simple, focus on CMS-specifics and include pointers to more information.
VIDYO PIN is 1234
Basic concept is to have two half-day sessions for newcomers, both students and more experienced people. First half day is a series of introductory talks/discussions. Second half day includes a visit to P5 and other CMS experimental areas (904, TIF, 892 etc.)
Main presenters and discussion leaders should be the CMS Management, Subsystem Managers and Coordinators. Presentations should be simple and include pointers to more information.
Overview of CMS objectives, “CMS detector design drivers” and “major decisions”, present detector - including magnet, results so far. Also include management structure (systems, coordination areas), role of the CB, decision-making process, long-term plan (including upgrades in Phase I and Phase II). Brief intro to LHC operations inc. lumi measurements and safety aspects (BRiL)
Overview of particle tracking using the pixels + tracker + muon detectors, including descriptions of each detector, alignment loop, project organizations, people. Needs input from AlCa, TK/MUON POG. Example results of performance - vertex location precision, pT resolution, 2-track separation, muon id efficiency, muon trigger efficiency etc. as functions of pileup (# vertices). Longevity & upgrades.
(KIT - Karlsruhe Institute of Technology (DE)), Jay Hauser
(Univ. of California Los Angeles (US))
Overview of the history of the CMS calorimeters, their construction/assembly, issues that have arisen during Run I of the LHC, detector performance, benchmark physics processes and long-term prospects (to 2035). Brief overview of ECAL and HCAL organisation.
(CERN), Pawel De Barbaro
(University of Rochester (US))
Video in CDS
Afternoon practicalities10m503-1-001 - Council Chamber
Overview of offline workflows for the preparation of the data for publications. The talk covers topics in the area of Offline, Physics Performance and Datasets (PPD and Computing: prompt reconstruction and Prompt Calibration Loop, Datasets,
Data distribution and Tier structure of our computing, CMS software (CMSSW), Validation and Data Quality Monitoring, MC Production, Alignment & Calibrations, Data Certification, Luminosity bookkeeping.
Overview of organization, publications workflows and related committees: publication committee, statistics committee, etc. CMS specifics like particle flow, analysis release, how to access the data and summary of main aspects of CMS data analysis school will also be given. The physics analysis objectives for 2015 and beyond, based on Run1 results, will be summarized.
Overview of CMS schools (data analysis, upgrade etc). code of conduct, computing rules, communication aspects (hypernews, egroups, meetings, WGM), CMSSW practicalities, the .cms network. Expectations from being a member of CMS (EPR, shifts, authorship). Secretariat (CMS and user’s office), conferences (CINCO, rules for assigning points, priorities, how/who can nominate), publications (CMS Notes of all types, journal publications etc.), CMS guiding