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:
(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), Dohun Kim
(Physikalisches Institut University of Heidelberg), Frank Meier Aeschbacher
(Universität Heidelberg), Heiko Augustin
(PI Uni Heidelberg), Lars Noehte
(PI Heidelberg), Luigi Vigani
(University of Oxford), Lukas Mandok
(Physikalisches Institut Heidelberg), Sebastian Dittmeier
(Physikalisches Institut, Universität Heidelberg), Thomas Theodor Rudzki
(Physikalisches Institut Heidelberg)
Present: Sebstian, Lukas, Lars, Andre, Thomas, David
Vidyo: Alena, Jan, Luigi
Minute-taker: Annie (we go through the year in alphabetical order, first name)
Andre: 15 week of beam request to PSI (2 week timing detectors, 2 week radiation test, 3 week pixels, 6 week of bean at the end of the year (install the magnet, beam characteristion with and without the magnet during 3 weeks, then 3 more weeks to set the sub-systems and the DAQ)). We need cooling for the pixels.
David (presentation): Preliminary ATLASPix3 Testbeam Results. Scans of different DAC Setting and 5 ATLASPix3 Sensors in the MuPix8 telescope.
Talk about introduce AtlasPix3 to PSI for beam monitoring. Alena sensor (with hit counters) should work better for beam monitoring
AtlasPix list of task (David):
1.Powering problem, Lukaz looking into this
2. clock problem?
3. Software (Ex. ToT spectrum should be check)
4. Implementation of external injection
5. Check for use of sorted data
6. Eyes diagram for different frequencies
7. Power comsumption
8. Measured of voltage directly in the bond pads
Luigi: Integration test will be better with MuPix8 which run to full speed.
Andre: Single pixel efficiency should be test at PSI. Better single pixel timing. Next DESY test beam shouls work for: Be sure that everything is running (sortred). CLEANING OF THE SORTWER HIGH PRIORITY!!
David: who will design the insert for MuPix X???
Heiko: Writting the documentattion for MuPix X. First version tomorrow will be send around.
Thomas: Computer not working, no too much progress. Noise and S curve for serial powering should be test in test beam? Andre think just in the lab, we know alredy the sensors have high efficiency (just depend of the threshol, the voltage and radiation).
Annie: Working in the BDV for AtlasPix3
Lukas: Infrared camera from the workshop to test hot points in the insert for search for volatge drops, any visible hot spot.
Sebastian: Prepering slides for the colaboration meeting. Design of cooling of the frontßend board. Aluminium plate in top of the front-end board. A plate in top with a heating pipe.