data acquisition requirements and concepts

20
2.3.2005 P. Heimann, Design Review March 2005 1 Data acquisition requirements and concepts Requirements Data acquisition task Long pulses General issues Concepts Time tagged data Stream model Configuration Time groups Synchronous analysis Monitoring Message system Networks XDV Group

Upload: trula

Post on 20-Mar-2016

52 views

Category:

Documents


1 download

DESCRIPTION

Data acquisition requirements and concepts. Requirements Data acquisition task Long pulses General issues Concepts Time tagged data Stream model Configuration Time groups Synchronous analysis Monitoring Message system Networks XDV Group. W7-X Stellarator. Data acquisition task. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 1

Data acquisition requirements and concepts

RequirementsData acquisition taskLong pulsesGeneral issues

ConceptsTime tagged dataStream modelConfigurationTime groupsSynchronous analysisMonitoringMessage system

NetworksXDV Group

Page 2: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 2

W7-X Stellarator

Page 3: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 3

Data acquisition task

• In the final stage there will be about 100 diagnostic systems

• Collect data from the diagnostic hardware• Store and archive data for common access in

time• Data should be stored in a global space• Data from all systems have to be comparable• Configuration for the system on a global scale• Handle data for long pulses

Page 4: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 4

Long pulses

• Discharges up to 0.5 h– new concept for data acquisition– new structure of archived data– segment concept

• Global time• Data monitoring• Remote control, automatic execution• Message logging• Data reduction• Pattern recognition, event driven sampling• Real time for feedback

Page 5: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 5

General requirements

The system should be• Flexible• Extendable• Maintainable

No early decision on computer hardwareAs far as possible independent of a special operating systemAs far as possible use mainstream hardware components and

softwareUse already proven concepts from existing systems

Modern software design principles, Object oriented methodsObject oriented data baseJava as implementation language

Page 6: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 6

Global timing system

0 10 1 2 3 4 5 6 7

clk gate

cTTE

UTDC

ADC

Central timer system

DAQ station

lTTE

Control system

Optical star

Patch panel64 bit counterbit 0 = 1 nano secondtime resolution 10-20 nsec

Clock and time synchronized64 bit local counter

Page 7: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 7

DAQ Station DescModule Desc

Module Desc

DAQ Station DescModule Desc

Module Desc

Exp. program

segment

segment

Data Acquisition (DAQ) System

DAQ Station

Archive

DatabaseMonitor-server

Event-builder

Controlsystem

Monitordistribution

Eventdístribution

Analysis-system

DAQ Client

Data stream model dataparameter Logdischarge programconfiguration

DAQ Station DescModule Desc

Module Desc

sensors

actuators

DAQ a

control a

control b

DAQ bmeasure

setupSync. Analysis

Message logging

Page 8: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 8

Configuration

Database

ControllableModule

SegParStatusPar

Module

EnvPar

Parameter Log

EnvPar: fixed parameter for one dischargeSegPar: parameter, that can change over the discharge time, segment parameterStatusPar: any kind of status information generated by the module

ModuleDescEnvPar

Segmentchange

Page 9: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 9

Time Group Concept

TDC Module1

Control Module0 - *

Analysis Module0 - *

Data Module1 - *

Time Group Time Groups:

•RtTimeGroup•ContinuousTimeGroup•PulsedTimeGroup•SVTimeGroup•NetTimeGroup•AUGTimeGroup

Device Stream

PPG Module0 - 1

Hardware Module

Page 10: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 10

Time Groups

TimeGroup DAQMode Description

rtTimeGroup continuous

Read time and data in small blocks, the blocksize is dependent on the time scale of the synchronous analysis processes. Data is collected to larger blocks and then transferred to the storage. May have all types of analysis processes.

ContinuousTimeGroup continuousRead time and data in large blocks by DMA. Data is transferred continously to the storage. No synchronous analysis tasks are available

PulsedTimeGroupstart/stop or pre/post

Time and data is stored in hardware memory and read out after a trigger occured. Data is transferred to the storage and the acquisition is started again. Synchronous analysis processing possible.

SVTimeGroup

pre/post on larger scale, like continous

Time and data is collected like in a rtTimeGroup, but no data is transferred to the storage. If an external or internal event is detected the amount of data defined is transferred to the storage. All types of analysis processes are possible. For internal event detected a pattern recognition process is necessary.

NetTimeGroup continuoussame time group as rtTimeGroup, data is read from network interfaces instead of data generating devices.

Page 11: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 11

DAQ Device

Interface Device:

public Parmset update(int subDev, Parmset p)public void initialize(int subDev, Parmset env, Parmset def)public Packet genPacket(int subDev, int packetSize)public void startDAQ(int subDev)public void stopDAQ(int subDev)public boolean readData(int subDev, Packet p, int length)

Operating SystemDriver

C++ InterfaceJNIHardware

Hardware:

fast accessdirectly accessible from computerbuffered by FIFO memorydrivers available for common operating systems

Device DEVslot Nr

SubDevice0SubDevice1SubDevice2..SubDeviceN

API

Page 12: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 12

DAQ Streams

OutputStream:

public void insert(Object obj)public void close()

DatabaseObjectStore

Local File

Field

.....

Streams:

DbaseFifoOutChannelDCacheFifoOutChannelLogFifoOutChannelFileInChannelFileOutChannelFieldInChannelFieldOutChannel

InputStream:

public Object extract()public void close()

Page 13: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 13

DAQ Analysis Modules

ControllableModule

Timegroup&AnalysisModule&OutputStream&

AnalysisModule

Timegroup&AnalysisModule&OutputStream&

AnalysisModule

output

input

DataModule

..OutputStream&.. input

0-1

0-*

TimeGroup

DataModule&..

1-*

AnalysisProcess

Timegroup&AnalysisModule&OutputStream&

AnalysisModule

FunctionUser supplied function

Synchronous Analysis Processes:

DataReductionProcess: generates a reduced data stream, used for monitoringFeedBackProcess: generates data for feedback purposes, real time dataPatternRecognitionProcess: processes data and looks for patterns, event detection

Page 14: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 14

Monitor System

Data base

Monitor server

Monitor Process A

Monitor Process B/N

Monitor parameter,Analysis functions

Clients

stream A

stream N

Signal A

Signal B

Fields Fields

stream B

DAQStation

DAQStation

DAQStation

Multicast Multicast

Page 15: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 15

Soft X-Ray

400 channels200 KHz

Data reduction30Hz

MonitorServer

Neural Network

MonitorProc

MonitorClient

Visualizer

DAQ Station

CIPSUdo v. Toussant Sylvio Gori

FileReader

Data File

DoublePacket(55)GifImageVisualizer

Image Prod

pvm

55 double 30x30double

MonitorProc

pvm

Linux

SoftX

Page 16: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 16

Monitor System

Web Clients

MonitorSignal A

MonitorSignal B

Fields WebServerhttp

Servlet A

Servlet B

Web Access

Page 17: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 17

Message Handling

MessageHandler

FieldReceiverReceiver SpecialReceiver

onMessage(String medium, int id, Packet message)

messageReceived(String medium, Packet message)

ProgramManager ProgramLoader SelectionProcessConsumer

sendMessage(String medium, Packet message)

IF: MessageConsumer

IF:MessageSender

consumerList

messageQueue

IF: MessageReceiverregisterComsumer(String medium, int id)unregisterConsumer(MessageConsumer consumer)

FieldInChannel

Page 18: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 18

Network Resources

eth0 eth1 znyx0 TDC1 TTE1 Sbit3

Messages Monitor FeedBack

rtNetstdNet Special hardware

Interfaces

FieldInChannelFieldOutChannel

timerNet

UDP Layer2TransportAddress

Logical Network

ComputerDesc

Page 19: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 19

DAQStation

Networks

Real Time Net

DAQ-Net

Control Net

DAQStation

Public Net

C C W7X-Control

S S

S

R

R

R

Multicast enabled on alllocal networks

Central Timer

Archive

Page 20: Data acquisition requirements and concepts

2.3.2005 P. Heimann, Design Review March 2005 20

XDV Group

P. Heimann (RZG) CoDa software, designCh. Hennig (W7-X physics) Monitor server, networkingH. Kroiss (E2) Data base applicationsG. Kühner (W7-X physics) System configuration, designH. Kühntopf (W7-X physics) Monitor clients, data base

applicationsJ. Maier (RZG) Data base systemJ. Reetz (RZG) (->2004) Video systemsM. Zilker (RZG) Hardware support, hardware

implementation

Topics: