Meeting Agenda

23 March 2004

In attendance:  J. Nelson (notetaker), J. Frisch, R. Fuller, R. Hall, J. Rock, R. Chestnut


Timetable for Checkout 
We’re expecting hardware Friday.  On Monday get signals and triggers wired to hardware.  Morning of the 30th – realistic signals everywhere – start software checkout.  Calibration stuff – I&Q->A&P will be done offline.  ADC volts to power calibration   Middle of next week probably.

     Processing Loop needed Monday, April 5 time early. (Ron out of town 4/2-4.)


Slow archiver? 
Janice and Bob will see if WFM acquisition speed has improved and measure it.


Secret Decoder Ring 
Need to expand Steve’s spreadsheet of Channel map to include Base Addresses (full 32-bit VME address) for modules and slot locations. (Judy is gonna help out with this.)


SLED FDBK through SCP slow feedback

     (still true) Ed did a wonderful job creating this, but unfortunately we haven’t had a chance to test it yet (hardware problems/tests).  4/1st probably.

Janice will send Ed a warning email that this is coming soon.


SIS waveforms archived every hour (plus on change)

     (still true) We do want this and around early April.


Database and Displays

Judy has booted in new LLRF PVs – PWRs and ENs and WFs.

Display changes are underway.  Joe points out lower level displays are needed sooner – early next week, than those showing PWRs and things like that.

A&P much lower priority. (until we can watch SISes without archiving the data)


Processing Loop status

Processing Loop status – ongoing.  Hopefully some progress this week.

Janice provided to Ron (and at the end of these minutes) the equations for missing energy needed.


macnair module support of aes

(no new news until proc loop done)Basic database is there and works now in TR09 and TR06.  (yeah)  Then Ron has a bit more database stuff to install.  RMS/BIG requirements for 8-packs structures: Ron gets to choose which is easier – one loop for all MacNairs in tr09 and tr06, or one loop for each ioc


Will need to be able to archive and set the gain (internal to module). (potentially different for each module)

Will need to have AES on structures in tunnel April 1stish


PLC checkout

(still true) Janice is finished preparing the list. She hopes to start doing some of the checkout this week.



Has been installed.  Cassel still doesn’t have it on the network with its own unique id.  Once that’s there, Janice can modify DCM/PLC5 code to get them to EPICS.  Judy has the list for making the database.  Janice is working on support panels.


2-pack PLC coming in April-ish. 

(still true) ~20 signals as yet undefined.  Janice will ask for TP printouts for this PLC too…


NLCTA/8-pack summary display

(still true) Ron said he’ll ask a SWE person to make it so DM displays can be CUDified (and Webified thereafter).  Once the DB is in place (2nd priority after the proc loop), Janice will do final tweaks to the display and we’ll be ready for CUDification.


Requests to not lose

-Target Power on trs8 (trs1 & 2 too?) proc loop input panel (user enterable real, cmlog on change, save/restored)

-Missing energy for SLED and WGs



The Processing Loop Missing Energy Plan

Here's the plan for calculating missing energy in the structures and sled system:


There are enough cables/hardware to instrument two of the structure input forward couplers.  The plan is to instrument structures 6 & 8 (if they are numbered 5-8 from up- to downstream).  The missing energy for

structure 5 is struct 5 output forward - struct 6 input forward

struct 6 missE = struct 6 outfwd - struct 6 infwd

struct 7 missE =  struct 7 outfwd - struct 8 in fwd

struct 8 missE = struct 8 outfwd - struct 8 in fwd


We will also ask software for a SLED missing energy and two waveguide missing energies calculated as such:

SLED missE = sled M01 outfwd - sled m01 infwd

WG6 missE = sled M01 outfwd - struct 6 in fwd

WG8 missE = sled M01 outfwd - struct 8 in fwd

that will not be used in the processing loop but will be displayed on a panel and be archived.


All equations will have the form A-B*C, where C is a user-enterable constant on a diagnostic panel.