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:
(University of Manchester (GB))
Mark William Slater
(University of Birmingham (GB))
UK HEP System Managers Pre Meeting Workshop on Ganga.
Ganga is pure python but for this workshop, we recommend running the CernVM on a laptop. Run through the tutorial here:
This will get you a system that can not only try out Ganga but also submit to the GridPP Dirac service.
If you don't have access to the GridPP Dirac service or just want to try out Ganga on local backends, any SL6 installation should work though having CMVFS would be an advantage. Running from Lxplus would be the obvious choice here.
This session will cover running jobs on different backends including DIrac. It will also look at how Ganga handles input and output data with for it's jobs. It will cover the following sections in the tutorial: