TTF/FLASH 9mA Meeting webex meeting - Draft
22 June, 2008

Attendees
J. Carwardine
N. Arnold
V. Ayvazyan
O. Hensler
T. Wilksen
S. Michizono

Agenda Topic: Controls, DAQ, screens for 9mA studies in September

Discussions of topics and tasks based on slides from John Carwardine and Ned Arnold. See ilcagenda for the list:
http://ilcagenda.indico.cern.ch

Notes

DOOCS servers are being written for ACC456 by Jarek S. The servers are based on ACC1, but with several improvements (not a good set of property names now). Property names will be different to those in ACC1 now. At a later date, ACC1 server will be replaced with the new one being developed for ACC456. Jarek will also generate the server for ACC23. The new property lists are not yet available.

Several new ddd displays are needed: interfaces with the new SimconDSPs, 

Many of the RF waveforms are digitized twice: by both the LLRF systems themselves and by the monitoring ADCs of the DAQ. Examples include cavity probes, forward/reflected powers, etc. Currently only the monitoring ADC data is collected in the DAQ. For the 9mA tests, we wish to collect both.

A detailed list is needed of DOOCS properties considered 'critical' for the 9mA tests and hence must be collected in the DAQ. Ned showed a preliminary list, largely based a one-year old list from Mariusz. Ned will send the list to Valeri and Olaf for their review and to add other channels.

The critical-channels list will include spectrum waveforms collected at 1MHz for each pulse, slow-scan scalar data, and key setpoints and feed-forward waveforms.

Ned noted that the property names in the DAQ do not completely line up with the property names in DOOCS. Olaf will assist with the translation from DOOCS to DAQ property names.

Data is collected from the DAQ via Matlab commands. A GUI interface exists to view available data and to make plots. This is the DAQ_Data_gui javascript application.

Olaf reported that the disk array for storing 9mA DAQ data has been ordered.
The DAQ will be set up with a dedicated data stream to the 9mA disk area. The normal DAQ data stream will be turned off.

It would be helpful to have a mechanism to log specific time-ranges of interest for subsequent analysis. Clearly using the FLASH e-log is one convenient option. Tim suggested doing what the experimenters do, which is to only enable the DAQ data streams when they are collecting data, and to disable it otherwise. [JC note: there is almost certainly a subset of data that we would want to collect continuously, but certainly not the entire set]

Tim and Olaf noted that several tools already exist for accessing DAQ datasets. Data is extracted from the DAQ using Matlab commands.  There is a jDDD DAQ tool called DAQdataGUI-experimental.jnlp available from the doocs applications page or from the DOOCS ddd display off the main FLASH ddd display. It was reported that this tool can do correlations between signals. John and Ned will work with the tools to understand what is available. Kay Rehlich would be the contact person for the jDDD applications. Tim would be the contact person for any DAQ related questions. Vladimir Rybnikov wrote the Matlab applications to acces the data.

It was reported that the DAQ has already been modified to collect the full-length LLRF spectrum waveforms (2048 samples covering 2ms).

The LLRF group is working with ... to implement a separate triggered data capture system for the LLRF waveforms. This would capture data only if a particular trigger event occurs.

Olaf has already written a quench detection application, which is under test now.

MPS/BIS interfaces are needed to the ACC456 and ACC23 stations. Valeri is following up.