The Clock Files are stored on d0ola in ~trgmgr/master_clock/config_files. Terminology: Tick = 132 ns, RF Bucket = 18.8 ns Ver Comments --- -------- 1 can be used to start the clock after loss of power no Subsystem Gap or Strobe standard file prior to adding Subsystem signals 2 Subsystem Gap 2.25 usec before Synch Gap Marker use with TRM 35.1 3 Subsystem Gap 467 ns after Synch Gap Marker use with TRM 39.1 THIS IS NOW THE STANDARD FILE The timing in the subsequent files is relative to the timing here. 4 Synch Gap Marker 2 Ticks / 7 RF Buckets later 5 Subsystem Strobe 4 RF Buckets earlier so it rises with the Subsystem Gap signal 6 Subsystem Strobe 3 RF Buckets earlier 7 Subsystem Strobe 2 RF Buckets earlier 8 Subsystem Strobe 1 RF Bucket earlier 9 Subsystem Strobe 1 RF Bucket later 10 Subsystem Strobe 2 RF Buckets later 11 Subsystem Strobe 3 RF Buckets later so it rises as the Subsystem Gap falls this is also when the TRM Clock Rises 12 Subsystem Strobe 3 RF Buckets later Subsystem Gap 3 RF Buckets later so the Gap rises and then 4 RF Buckets later the Strobe rises at the same time as the TRM Clock 13 Subsystem Gap 2 Ticks earlier 14 Subsystem Gap 21 Ticks / 147 RF Buckets later 15 Subsystem Gap 22 Ticks / 154 RF Buckets later 16 Subsystem Gap 148 RF Buckets later Subsystem Strobe 1 RF Bucket later to maintain correct phase with Subsystem Gap 17 Subsystem Gap 149 RF Buckets later Subsystem Strobe 2 RF Buckets later to maintain correct phase with Subsystem Gap 18 Subsystem Gap 150 RF Buckets later Subsystem Strobe 3 RF Buckets later to maintain correct phase with Subsystem Gap 19 Subsystem Gap 151 RF Buckets later Subsystem Strobe 4 RF Buckets later to maintain correct phase with Subsystem Gap 20 Subsystem Gap 152 RF Buckets later Subsystem Strobe 5 RF Buckets later to maintain correct phase with Subsystem Gap 21 Subsystem Gap 153 RF Buckets later Subsystem Strobe 6 RF Buckets later to maintain correct phase with Subsystem Gap 22 official release of version 3 but it's almost twice as large and doesn't work 23 moves the Beginning of Turn so that the first live crossing corresponds to Current BX Number 7 moves and lengthens the Synch Gap so that it is the same as the Cosmic Gap but happens only once per turn adjusts and lengthens the Subsystem Gap so that it is positioned correctly with respect to the Synch Gap adjusts the Cosmic Gap so that it isn't active until the time when the next live crossing marker would be asserted if it weren't a gap period This is now the new "standard" file but hasn't been checked into CVS. 24 shifts Subsystem Gap signal five 132 ns Ticks later so that it now rises approximately 1120 ns after the Synch Gap 25 Spare Marker signal is asserted every 396 (lined up with the Interaction Marker) and continues in the Gaps. The jump in this pattern is in the middle of the gaps. 26 shifts Subsystem Gap 25 RF buckets earlier than ver 24 but did NOT move Subsystem Strobe the Subsystem Gap now rises only 1 RF bucket before the Subsystem Strobe 27 shifts Subsystem Gap another 3 RF buckets earlier than ver 26 so that the Subsystem Gap now rises 4 RF buckets before the Subsystem Strobe. Also adds the CFT LED Pulser Trigger signal on TL 13. 28 puts the sequencer into Sync mode (up until now it has been in Freerun mode) 29 put the PCC into Freerun mode (up until now it has been in Normal mode by default - that is, it powers up in Normal mode) the sequencer is still in Sync mode 30 put the sequencer in Freerun mode; the PCC is still in Freerun mode 31 sequencer in Sync Mode; PCC explicitly put in Normal mode 32 don't talk to the PCC (so it's current state remains - from power up, this should be normal mode) reset the sequencer and then put it into Sync mode it turns out to be quite important to reset the sequencer to make sure you get a clean start 33 reset the sequencer and put it into Sync mode put the PCC into Freerun mode 34 reset the sequencer and put it into Sync mode put the PCC into Normal mode 35 PCC into Freerun, Sequencer in Sync mode move Subsystem Gap 133 RF buckets later hopefully this means that it is happening only very slightly before the Sync Gap in the TRM (which is delayed relative to the master clock Sync Gap) Subsystem Strobe still rises 4 RF buckets after Subsystem Gap by coincidence, TRM clock rises at the same time as Subsystem Gap falls ideally in this version, the data is latched by the TRM Clock on the 3rd RF bucket after it is written by the Subsystem Strobe 36 as with 35, but Subsystem Strobe rises 5 RF buckets after Subsystem Gap i.e. only 2 buckets before the TRM Clock rises so the data has even less time to make it to the output latch 37 as with 35, but Subsystem Strobe rises 6 RF buckets after Subsystem Gap i.e. only 1 bucket before the TRM Clock rises so the data has even less time to make it to the output latch 38 as with 35 but the Subsystem Gap has been moved 1 RF bucket later as has the Subsystem Strobe this means that there is still 18.8 ns of hold time after the Subsystem Strobe but that the Subsystem Strobe is rising at the same time as the TRM clock, i.e. the data is being written at the same time it is being latched so this shouldn't work 39 move Subsystem Gap 7 RF buckets later than version 35 hopefully this means that it is happening only very slightly before the Sync Gap in the TRM or perhaps even after it Subsystem Strobe still rises 4 RF buckets after Subsystem Gap and 3 buckets before the TRM Clock 40 as with 39, but Subsystem Strobe rises 5 RF buckets after Subsystem Gap i.e. only 2 buckets before the TRM Clock rises so the data has even less time to make it to the output latch 41 as with 39, but Subsystem Strobe rises 6 RF buckets after Subsystem Gap i.e. only 1 bucket before the TRM Clock rises so the data has even less time to make it to the output latch 42 as with 39 but the Subsystem Gap has been moved 1 RF bucket later as has the Subsystem Strobe this means that there is still 18.8 ns of hold time after the Subsystem Strobe but that the Subsystem Strobe is rising at the same time as the TRM clock, i.e. the data is being written at the same time it is being latched so this shouldn't work 43 as with 35, but both the Subsystem Strobe and Gap have been moved 1 RF bucket later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises only 2 buckets before the TRM Clock 44 as with 35, but both the Subsystem Strobe and Gap have been moved 2 RF buckets later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises only 1 bucket before the TRM Clock 45 as with 35, but both the Subsystem Strobe and Gap have been moved 3 RF buckets later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises at the same time as the TRM Clock 46 as with 39, but both the Subsystem Strobe and Gap have been moved 1 RF bucket later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises only 2 buckets before the TRM Clock 47 as with 39, but both the Subsystem Strobe and Gap have been moved 2 RF buckets later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises only 1 bucket before the TRM Clock 48 as with 39, but both the Subsystem Strobe and Gap have been moved 3 RF buckets later, i.e. there is still good setup and hold time for the Subsystem Gap, but the Subsystem Strobe rises at the same time as the TRM Clock