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:
Tgm Video: Java application devoted to the monitoring of the timing events distribution. Through this tool it is possible to investigate what is currently played from the timing perspective. Played cycle, user, particle etc...are some of the information that can be retrieved as well as detailed information about the type of event that happened (telegrams details). The new history-record feature will be presented. [~10 minutes]
BcdSet Viewer: graphical Java application useful to investigate and have extra information about Bcd-sets, the different machines' cycles (spare and normal beams), their relations and dependencies. After it has been played it is also able to display the last played super-cycle. [~10 minutes]
jTimDiag: local timings' configurations and connections can be displayed and monitored from this Java tool. From the graphical layout it is possible to start direct acquisition and displaying the different settings cycle by cycle. Acquisition can be recorded and investigate step by step. A history page can also be generated showing the relations between local timings firing, basic period telegrams and central timing events (CTIM) [~20 minutes]
MTG Diagnostic: this tool provides a set of views to understand the behavior of all accelerators in the LIC domain (CPS,PSB,SPS,LEI). It helps to identify why a beam is not executed or to understand accelerator behaviors on certain circumstances.
Introduction: why new diagnostic tools? [~5 minutes]
CTIM application: This Web tool is aimed at monitoring and checking the configuration (static in Control Configuration DB and real time hardware settings) of the different CTIM devices in the available Central Timings. The hierarchy of the different devices is shown in a tree in order to underline the specific dependency for each event that runs on the GMT cable. [~8 minutes]
ExtCond: The External Conditions and FIDO programs Web tool goal is to put in place a complete monitoring system for external conditions in LIC Central Timing, showing their static and hardware configurations as well as their history. Through the monitoring facilities it is possible to follow the external conditions status in time. The application allows also to read and check which FIDO programs are currently in production. [~15 minutes]
Tide Dashboard: This dashboards started as a Timing Expert tool to investigate the status (with statistics and real time acquisitions) of the new TIming Distribution over Ethernet system, along with its timing distributors and providers. This tool turned out to be useful in understanding and finding issues in all processes that make use of the Timing facilities. It is possible to understand why a front-end and/or a process is loosing events, where it is connected etc. It is also useful to give a cardiogram of the current situation for the Timing users (answering question like "is the problem relative only to my machine or it’s a global issue?"). [~10 minutes]
FEC Navigator: This multi-purpose tool is used to investigate how a front end is configured from the hardware and software points of view relatively to the Timing system. Which hardware modules are installed, how are them configured, which LTIM are installed on a given front end (and vice versa where is an LTIM installed)....etc are some of the questions that can be answered using this tool. It is possible to inspect Local Timings and check further details using jTimDiag Java application using direct links. [~20 minutes]
Description of the CCM Editor
• The main concepts
• CCDB servers used by the CCM Editor
• How to launch the CCM Editor
• RBAC security considerations
Live demos of some edition use cases:
• Editing the CCM Menu tree
• Editing Applications, Tools & Substitution entity definitions
• Editing the Operational Configurations
• The Application Checker tool
Links to the CCM Editor help, the F.A.Q. and JIRA