BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//CERN//INDICO//EN
BEGIN:VEVENT
SUMMARY:TTC news - December 2004
DTSTART;VALUE=DATE-TIME:20041202T090000Z
DTEND;VALUE=DATE-TIME:20041202T110000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-42261@cern.ch
DESCRIPTION:http://indico.cern.ch/conferenceDisplay.py?confId=42261
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=42261
END:VEVENT
BEGIN:VEVENT
SUMMARY:TTC news - June 2005
DTSTART;VALUE=DATE-TIME:20050603T080000Z
DTEND;VALUE=DATE-TIME:20050603T100000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-42260@cern.ch
DESCRIPTION:http://indico.cern.ch/conferenceDisplay.py?confId=42260
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=42260
END:VEVENT
BEGIN:VEVENT
SUMMARY:TTC news - December 2006
DTSTART;VALUE=DATE-TIME:20060124T090000Z
DTEND;VALUE=DATE-TIME:20060124T110000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-42259@cern.ch
DESCRIPTION:http://indico.cern.ch/conferenceDisplay.py?confId=42259
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=42259
END:VEVENT
BEGIN:VEVENT
SUMMARY:RF2TTC review
DTSTART;VALUE=DATE-TIME:20060502T120000Z
DTEND;VALUE=DATE-TIME:20060502T160000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-2976@cern.ch
DESCRIPTION:http://indico.cern.ch/conferenceDisplay.py?confId=2976
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=2976
END:VEVENT
BEGIN:VEVENT
SUMMARY:TTC upgrade - Production Readiness Review
DTSTART;VALUE=DATE-TIME:20070208T080000Z
DTEND;VALUE=DATE-TIME:20070208T110000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-12273@cern.ch
DESCRIPTION:Production Readiness Review of the TTC upgrade system\n\nhttp:
 //indico.cern.ch/conferenceDisplay.py?confId=12273
LOCATION: 4 - R - 017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=12273
END:VEVENT
BEGIN:VEVENT
SUMMARY:RF & TTC Questions and Answers meeting after LHC start-up
DTSTART;VALUE=DATE-TIME:20080923T070000Z
DTEND;VALUE=DATE-TIME:20080923T090000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-42253@cern.ch
DESCRIPTION:informal questions/answers session about timing signals during
  LHC start-up and for the final system\n\nhttp://indico.cern.ch/conference
 Display.py?confId=42253
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=42253
END:VEVENT
BEGIN:VEVENT
SUMMARY:RF cogging meeting
DTSTART;VALUE=DATE-TIME:20091105T090000Z
DTEND;VALUE=DATE-TIME:20091105T110000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-74019@cern.ch
DESCRIPTION:meeting between RF and experiments to define the procedure of 
 cogging and phase shifting of the RF for first collisions.\n\nhttp://indic
 o.cern.ch/conferenceDisplay.py?confId=74019
LOCATION:CERN 874-1-011
URL:http://indico.cern.ch/conferenceDisplay.py?confId=74019
END:VEVENT
BEGIN:VEVENT
SUMMARY:RF-Experiments Synchronization Meeting
DTSTART;VALUE=DATE-TIME:20100202T133000Z
DTEND;VALUE=DATE-TIME:20100202T150000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-81851@cern.ch
DESCRIPTION:Dedicated Timing meeting to take stock of what we learned duri
 ng LHC startup and prepare the restart. In particular:\n	*understand the B
 PTX and Vertex results of 2009 in relation to RF events\,\n	*from this exp
 erience\, decide what is the acceptable range (both from RF and experiment
 s) of Vertex and BPTX variations without requiring a warning and/or a reph
 asing. Or\, in other terms\, what is a 'wrong' phase\, from both RF and ex
 periments points of view.\n	*define a procedure for 2010 runs (phase align
 ment\, piquet service\, system monitoring)\n \nAGENDA:\n-----------------\
 nA. from 2009:\n	A.1. Feedback from RF point of view \n		*A.1.a. Summary o
 f RF phase jumps & explanation \n		*A.1.b. Vertex position shift versus RF
  events  \n		*A.1.c. sigma-z variation- impact on vertex position?\n		*A.1
 .d. Phase during ramp \n		*A.1.e. Clock quality and stability in Nov & Dec
 ember at the CCR (jitter\, jumps…)\n		*A.1.f. Conclusion: what should we
  expect as ‘normal’ variations of bunches & beam spot from RF point of
  view?\n	A.2. Feedback from experiments \n		*A.2.a. consistency of BPTX de
 ltaT versus Vertex? Resolution of BPTX measurements after calibration?\n		
 *A.2.b. How do experiments deal for deltaT with multibunching?\n		*A.2.c. 
 Which shift in beam spot position can experiments tolerate without requiri
 ng rephasing?\n		*A.2.d. Is there an impact of RF BC variations on the ver
 tex reconstruction?\n-----------------\nB. for 2010:\n	B.1. External clock
  handshake? Except during SETUP (and before IMMINENT)\, when may resynchro
  happen?\n	B.2. No synchronised Bcref for 2010 – check the agreement fro
 m experiments \n	B.3. Rephasing procedure for 2010:\n		*B.3.a. Will we use
  the BPTX to check the alignment? Should/could the data be published? Whic
 h format?\n		*B.3.b. Will the RF implement this automatic rephasing tool?\
 n		*B.3.c. If the phase is 'wrong'\, what should be the procedure? (expert
 s won’t be there night and day on a long term basis)\n		*B.3.d. If repha
 sing is done\, could it be during ‘stable beam’? If yes\, will the fee
 dback be given by vertex reconstruction? How fast is it (versus luminosity
 )?\n	B.4. RF Piquet\n		*B.4.a. Procedure for experiments to follow before 
 calling the Piquet service. Is it through CCC?\n		*B.4.b. Requirements of 
 registers publication on DIP for RF-Rx configuration check\n	B.5. Fibre ma
 intenance:\n		*B.5.a. EN-EL proposal \n	B.6. Drift versus temperature of t
 ransmitted RF signals\n\nhttp://indico.cern.ch/conferenceDisplay.py?confId
 =81851
LOCATION:CERN 4-R-017
URL:http://indico.cern.ch/conferenceDisplay.py?confId=81851
END:VEVENT
BEGIN:VEVENT
SUMMARY:BPTX publication on DIP and cogging
DTSTART;VALUE=DATE-TIME:20100222T140000Z
DTEND;VALUE=DATE-TIME:20100222T150000Z
DTSTAMP;VALUE=DATE-TIME:20130525T044503Z
UID:indico-event-85840@cern.ch
DESCRIPTION:Discussion on Massi and Sophie's proposal for BPTX publication
  over DIP\, synchro modes and cogging for startup.\n\nPROPOSAL:\n0) use DI
 P structure proposed in Alick's doc:\n   dip/EXPT/LHC/Timing\n\n1) zLocati
 onIP: indeed\, change to DeltaT in ns\n   Purpose: value for OP/EiC to fin
 e-adjust the crossing point\n   Definition: measure arrival time differenc
 e of paired bunches\n   (i.e. average over all bunch pairs __which are sup
 posed to collide in\n   the given IP__ )\n   Rate:  1 Hz (or less frequent
  ?)\n   NB: this requires colliding pairs for a given expt to give a value
 .\n   NB: cogging will be verified with proper bunch scheme (with pairs\n 
       that are supposed to cross in IPs. We do not have anymore the\n     
   pressure of last year.)\n\n2) PhaseB1 [ns]: phase difference between B1 
 (averaged over all bunches)\n   and bunch clock used by experiment.\n   Pu
 rpose: Monitor possible drifts which may lead to non-optimal detector\n   
 signal sampling. Offset to 0 as soon as experiment time alignment has been
 \n   performed.\n   Rate: currently 1 Hz\, but maybe overkill for drift mo
 nitoring.\n         0.1 Hz or 1/minute would be enough. No ?\n   NB: drift
 s we are looking for are of the order of 100 ps\, therefore\n   it is impo
 rtant that the published value be "baseline-subtracted"\n   to give a valu
 e which is not too far from zero (relative to 100 ps).\n   NB: if using BC
 \, this automatically reduces value to \n\nhttp://indico.cern.ch/conferenc
 eDisplay.py?confId=85840
LOCATION:CERN CCC-LPC
URL:http://indico.cern.ch/conferenceDisplay.py?confId=85840
END:VEVENT
END:VCALENDAR