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 College London)
Supporting Monte Carlo generators at the LHC20m
Working group meet on Tuesday 18th AM.
The general support of Monte Carlo services for the LHC is currently delegated to
LCG. The workshop offers an opportunity to re-evaluate some of the issues
dealing with the development and maintenance of the Monte Carlo software
relevant for both the experimental and the theoretical communities.
We will use this workshop to (1) discuss issues regarding
the use of jet algorithms at the parton, hadron and detector
level, (2) review the experience at the Tevatron, and (3)
try to arrive at some accords that will apply at the LHC.
Status of GENSER: presentation of the release 1_4_0 and plans30m40-SS-C01
Discussion and surprise about the delay with inclusion of new versions of HepMC in SCRAMToolBox. Lynn's advice to include ASAP at least 1.26.01 due to a serious drawback in 1.26.
Strong objections to changes of PDF sets in GENSER, even if this is a special GENSER version and agreed with the authors of a PDF set. Act only through the LHAPDF authors. Give more feedback to the LHAPDF authors.
Complaints about insufficient attention to SHERPA and insufficient collaboration (or no collaboration at all) with the authors.
CEDAR: HZTool is desirable in GENSER although it is in Fortran and the c++ substitution is in preparation.
CEDAR: Collaboration on Rivet and RivetGun (HepForge) welcome. Start when downloadable versions appear.
Experience with new compilers (G95 etc.)20m40-SS-C01
Discussion on collaboration with CEDAR30m40-SS-C01
(Department of Theoretical Physics)
Proposal of the new version of HepMC and discussion30m40-SS-C01
Some discussion about the options for HepMC.
There is no concern with the PdfInfo class, but we think that kf1 and kf2 should be renamed. See Torbjorn's talk in this session for better names.
There was some surprise expressed at the use of the FourVector != within HepMC.
We agreed to add generated mass as a double in GenParticle. In principle, experiments can choose not to save the generated mass. However, it is strongly advised that, if storage space is an issue, experiments should save the 3 momentum and the generated mass. The 4 vector can be safely reconstructed from 3 momentum and mass, but mass cannot always be safely reconstructed from the 4 momentum.
MCnet steering committee meeting4-3-004
First planning meeting of team leaders and the advisory
committee of the MCnet network
MCnet meetingTH auditorium
First meeting of all members of the MCnet network,
including presentations from any students or postdocs
who want to
What is MCnet all about? How can I benefit? What can