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:
Kickoff workshop for the new computing R&D projects to exploit the virtualization and multi-core technologies for the particle physics community. The idea is to bring together some of the technology vendors, the LHC collaborations and experts on the domain to share their experiences and needs in order to elaborate a possible program of work for the new R&D projects.
EVO Meeting available in "Universe" community.
It is also possible to phone in following this instructions http://evo.vrvs.org/evoGate/Documentation/EVO_Telephone_Bridge.pdf
Experience and plans on adapting software for multi-core
Introduction to the R&D project30m
ATLAS experiences running athena and TDAQ software30m
(High Energy Physics)
Experience in parallel programming using Python in LHCb30m
CMS experience and plans30m
First Results in a Thread-Parallel Geant430m
We have taken the TOP-C parallelization of Geant4 (based on MPI),
to semi-automatically create a thread-parallel Geant4 based on event
parallelism and a master-worker style of parallelism. We currently
address two issues:
1) detecting global variables and data structures, which must be
made thread-local. We modify the parser of the gcc compiler to
2) handling of random generator engines from CLHEP. This is needed to create
reproducible results by assigning known random seeds to each distinct thread.
The very preliminary tests show linear speedup with the number of cores,
up to the four cores of a quad-core processor. Future work will consider
moving some of the thread-local data back into process-global data,
in order to reduce the image size (eliminate separate copies per thread),
and to further ensure scalability for large experiments. We have also
demonstrated that our checkpointing package, DMTCP, works in this
thread-parallel environment operating in CERN 64-bit Scientific Linux.
(Northeastern University, Boston, USA)