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:
This review focuses on transverse beam instability diagnostic systems, in particular the bunch-by-bunch feedbacks, intra-bunch (i.e. head-tail & TMCI) and Q/Q' diagnostics.
The aim is to provide a first step in establishing a common understanding of what is needed, what could be useful for day-to-day operation, what could be delivered with the given resources, and to discuss and draft a recommendation of a targeted base-line after LS1.
Erik Van Der Bij
Nicolas Frank Mounet
Riccardo De Maria
Introduction and Mandate15m
What could be useful after LS1 -- an OP perspective30m
Review of existing systems and how they could be better integrated to aid day-to-day machine operation and handling (online diagnostics, post-mortem, pre-analysis of which parameter to tune etc.). Impact of instabilities on machine operation and LHC luminosity performance.
What is needed after LS1 -- an ABP perspective30m
Review of transverse instabilities already observed and expected with operation at increased beam energy and intensities after LS1, and functional requirements on diagnostics systems to better understand and cure these instabilities. Impact of instabilities on machine operation and LHC luminosity performance.
Summary of planned upgrades to the existing bunch-by-bunch feedback system for after LS1. Integration into Q/Q' diagnostic & FB infrastructure. Future options for after LS2. Required resources and time-line.
What could be delivered -- BI30m
Status and limitations of existing intra-bunch diagnostics systems. Summary of the proof-of-concept tests performed with beam in 2012 and potential application after LS1. Potential upgrades after LS2. Required resources and time-line.
Event Synchronisation and Logging Infrastructure - CO15m
Review options for synchronisation to propagate the information about an instability across the accelerator, the latency of the current mechanisms in the timing system.
(CERN), Jean-Claude Bau
Data storage, Post-processing and Visualisation Infrastructure - CO15m
Summary of the present system and upgrade plans during LS1 related to data storage, post-processing and visualisation infrastructure.
Summary and Recommendation1h
round table with stake holders -- discussion and initial recommendation.