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:
For Vidyo please use room extension 10823320 or use this link.
Reports of work progress
(Physikalisches Institut, Uni Heidelberg), Alena Weber
(Universität Heidelberg), Andre Schoening
(University Heidelberg, Institute of Physiscs), Annie Meneses Gonzalez
(PhD Student), Benjamin Weinläder
(PI Heidelberg), David Maximilian Immig
(Universität Heidelberg), Frank Meier Aeschbacher
(Universität Heidelberg), Heiko Augustin
(PI Uni Heidelberg), Jan Hammerich
(PI Heidelberg), Lars Noehte
(PI Heidelberg), Luigi Vigani
(University of Oxford), Sebastian Dittmeier
(Physikalisches Institut, Universität Heidelberg), Thomas Theodor Rudzki
(Physikalisches Institut Heidelberg)
DI: Testbeam report:
Many problems, main issue found just before start of data taking, newest version of firmware (stratix re-compile after aria5 merge) causes reduced DUT efficiency.
Very educational: Students learn a lot, introduction to analyse framework for DK.
Data taking about to start.
A lot of problems with Mimosa, due to old age.
LN: Presents Measurements with the flexprint bonded chip.
Eye Diagramm of Date link 4: 2.3 mV noise rms, 43.7ps, jitter rms; but small amplitude: 30 mV
DI: Did you look into the first link.
LN: not yet, but it was observed that link 1 was always systematically better than link 4 (PhD-Thesis Sebastian Dittmeier).
Eye obtained with setting with settings that minimised the drawn current.
Eyediagram reveals a slow rise time for the data signal, which explain why the amplitude is reduced on purpose, to allow a bit value change to happen in time.
LN:[presents frequency scan from the spectrum analyser]
Plot of Sync_reset and Ref_Clock path
Foundamental frequencies are marked with red lines 625 Mhz, 1.25 GHz, 1.875 GHz
Noise smaller than -60dBm.
Clear Amplitude drop around 1.25GHz
Plot unshielded twisted pair:
Overall damping, still need to look into it. Currently crocodile clamps used in parts of the setup (?)
AS: twisted pair runs better at high frequencies?? How much power is required for a succesfull signal transmission?
Is the scale correct? dBm or dB? really below 1mW signals? (-->take offline)