Status of InterCommunication on FeeControl Meeting Report Communication between DCS-Layers State of 2003-09-08 Sebastian Bablok Christian Kofler Ralf Keidel.

Slides:

Advertisements

Similar presentations

TRD-DCS Workshop, Zentrum für Technologietransfer und Telekommunikation FH-Worms FeeCommunication Chain Status of the FeeCom.

Advertisements

Zentrum für Technologietransfer und Telekommunikation FH-Worms FeeCommunication Chain Status of the FeeCom software Benjamin Schockert.

Zentrum für Technologietransfer und Telekommunikation FH-Worms FeeCommunication Chain Status of theFedServer Benjamin Schockert Sebastian.

TPC electronics meeting, /14 Zentrum für Technologietransfer und Telekommunikation FH-Worms FeeCommunication Chain Status.

PLDI’2005Page 1June 2005 Example (C code) int double(int x) { return 2 * x; } void test_me(int x, int y) { int z = double(x); if (z==y) { if (y == x+10)

13/04/2015Client-server Programming1 Block 6: Threads 1 Jin Sa.

Slide 3-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 3 3 Operating System Organization.

What is a pointer? First of all, it is a variable, just like other variables you studied So it has type, storage etc. Difference: it can only store the.

Module R2 Overview. Process queues As processes enter the system and transition from state to state, they are stored queues. There may be many different.

Exception Handling Introduction Exception handling is a mechanism to handle exceptions. Exceptions are error like situations. It is difficult to decide.

Client Side Programming Using Java Applet Outcomes: You will be expected to know: – Java Applets and HTML file; –bytecode and platform independent programs;

Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 13 Introduction to SQL Programming Techniques.

Dynamic Memory Allocation in C++. Memory Segments in C++ Memory is divided in certain segments – Code Segment Stores application code – Data Segment Holds.

1 Processes and Pipes COS 217 Professor Jennifer Rexford.

Normal text - click to edit FeeServer: (version 0.9.2) ( ) S. Bablok (IFT, University of Bergen)

Normal text - click to edit FeeCom software during TPC commissioning (Benchmarks) Sebastian Bablok Dag Toppe Larsen Matthias Richter Benjamin.

Low level telemetry software Marty Olevitch Washington U. in St Louis April 8, 2005.

Ceng Operating Systems Chapter 2.1 : Processes Process concept Process scheduling Interprocess communication Deadlocks Threads.

Chris Harrison Stacey Kuznetsov Mariya Lysenkova Jennifer Refat Gabriel Sinkin.

1 Introduction Chapter What is an operating system 1.2 History of operating systems 1.3 The operating system zoo 1.4 Computer hardware review 1.5.

TRD dcs workshop, Heidelberg, Jan 22, TRD Feeserver/controlEngine Kai Schweda, University of Heidelberg R. Bramm, B. Doenigus, T. Dietel, D. Emschermann,

1. When things go wrong: how to find SQL error Sveta Smirnova Principle Technical Support Engineer, Oracle.

Components and Concurrency in ESMF Nancy Collins Community Meeting July 21, GMAO Seasonal.

Normal text - click to edit RCU – DCS system in ALICE RCU design, prototyping and test results (TPC & PHOS) Johan Alme.

IT253: Computer Organization Lecture 4: Instruction Set Architecture Tonga Institute of Higher Education.

Today’s Topics Introducing process: the basic mechanism for concurrent programming –Process management related system calls Process creation Process termination.

Architectures Classic Client/Server Architecture Classic Web Architecture N-tier (multi-tier) Architecture FEN Databaser og Modellering.

Variables and Objects, pointers and addresses: Chapter 3, Slide 1 variables and data objects are data containers with names the value of the variable is.

By Noorez Kassam Welcome to JNI. Why use JNI ? 1. You already have significantly large and tricky code written in another language and you would rather.

Dynamic Memory Allocation Conventional array and other data declarations An incorrect attempt to size memory dynamically Requirement for dynamic allocation.

Copyright © 2009 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Dynamic Memory Allocation 9.8.

Process. Processes A process is an abstraction for sequence of operations that implement a computation/program. A process may be manipulated, suspended,

DCS – SDD Low Voltage Monitoring Jiří Král Czech Technical University in Prague, FNSPE Vojtěch Petráček Czech Technical University in Prague, FNSPE.

Programming with TCP – III 1. Zombie Processes 2. Cleaning Zombie Processes 3. Concurrent Servers Using Threads  pthread Library Functions 4. TCP Socket.

1 Chapter 2.1 : Processes Process concept Process concept Process scheduling Process scheduling Interprocess communication Interprocess communication Threads.

P. Chochula ALICE Week Colmar, June 21, 2004 Status of FED developments.

Registers are always 32 bit / 4 byte memory is accessed directly when memory cannot be accessed kind of flag is on.

FTP Server API Implementing the FTP Server Registering FTP Command Callbacks Data and Control Port Close Callbacks Other Server Calls.

H.-H. S. Lee 1 ECE3055 Computer Architecture and Operating Systems Lecture 10 Process, Thread Prof. Hsien-Hsin Sean Lee School of Electrical and Computer.

1 Developing Application in Distributed Computing Environment (DCE)

Process Architecture Process Architecture - A portion of a program that can run independently of and concurrently with other portions of the program. Some.

The Software Construction Process. Computer System Components Central Processing Unit (Microprocessor)

Communication Layers Protocol Commands Results Command Specs Command Framework Database Access PVSS Server TOC ,

What is exactly Exploit writing?  Writing a piece of code which is capable of exploit the vulnerability in the target software.

Operating Systems Process Creation

1 Computer Systems II Introduction to Processes. 2 First Two Major Computer System Evolution Steps Led to the idea of multiprogramming (multiple concurrent.

PHOS APD Bias Control Goal: To develop software for the PHOS APD bias control that uses the agreed ALICE standards for detctor control and coniguration.

JS (Java Servlets). Internet evolution [1] The internet Internet started of as a static content dispersal and delivery mechanism, where files residing.

Source Controller software Ianos Schmidt The University of Iowa.

Process Management Azzam Mourad COEN 346.

Chapter 2. System Structures

Dcs meeting, CERN, Mar 13  14, HV Control box HV Box from Athens Kai Schweda, University of Heidelberg P. Mantzaridis, A. Markouizos, P. Mitseas,

OS part I, , Part I Computer System Structures Department of Computer Engineering, PSUWannarat Suntiamorntut.

DCS for TRD Pre-trigger Ken Oyama Jan. 22, 2007 DCS Workshop in Heidelberg.

Int fact (int n) { If (n == 0) return 1; else return n * fact (n – 1); } 5 void main () { Int Sum; : Sum = fact (5); : } Factorial Program Using Recursion.

FEE Control DIM (Distributed Information Management ) as communication layer between TPC/TRD and FEE control/monitoring application at ALICE.

CS241 Systems Programming Discussion Section Week 2 Original slides by: Stephen Kloder.

Testing, Monitoring, and Controlling CORBA-based Applications Sudipto Ghosh Priya Govindarajan Aditya P. Mathur Baskar Sridharan Software Engineering Research.

Summary of TPC/TRD/DCS/ECS/DAQ meeting on FERO configuration CERN,January 31 st 2006 Peter Chochula.

CS241 Systems Programming Discussion Section Week 2 Original slides by: Stephen Kloder.

Maria del Carmen Barandela Pazos CERN CHEP 2-7 Sep 2007 Victoria LHCb Online Interface to the Conditions Database.

Realizing Concurrency using Posix Threads (pthreads)

Realizing Concurrency using the thread model

Dynamic Memory A whole heap of fun….

Dynamic Memory A whole heap of fun….

Realizing Concurrency using Posix Threads (pthreads)

Realizing Concurrency using the thread model

Realizing Concurrency using Posix Threads (pthreads)

Dynamic Memory A whole heap of fun….

Presentation transcript:

Status of InterCommunication on FeeControl Meeting Report Communication between DCS-Layers State of Sebastian Bablok Christian Kofler Ralf Keidel

FEE Server (DIM - Server on RCU - Card) FEE Server (DIM - Server on RCU - Card) FEE Server (DIM - Server) PVSS Server (DIM - Server) FEE Client (DIM - Client) InterCom Layer (Application layer) Database Access PVSS Client (DIM - Client) Layers , Status of InterCommunication on FeeControl CE (Detector specific)

Status of InterCommunication on FeeControl TOC Interface FeeServer - ControlEngine Sequence of communication FeeServer - ControlEngine Data access on InterComLayer ,

Interface FeeServer - Control Engine , Status of InterCommunication on FeeControl Interfacecalled byimplemented byamount of calls void initializeCE()FeeServerCEonce int publish(...)CEFeeServerzero to several times on start up void signalCEready()CEFeeServeronce int issue(...)FeeServerCEn - times void cleanUpCE()FeeServerCEonce

Interface FeeServer  Control Engine , Status of InterCommunication on FeeControl void initializeCE() Initializes the ControlEngine on the board. bus driver can be loaded Items for monitoring can be published runs in its own thread (controlable from FeeServer)

Interface FeeServer  Control Engine , Status of InterCommunication on FeeControl int publish(Item* item) Informs FeeServer about values for monitoring. gives „Item“ to the FeeServer name (char*) and location (volatile float*) [value] returns an error code, if call was unsuccessful, else 0 has to be called for every Item to be published

Interface FeeServer  Control Engine , Status of InterCommunication on FeeControl void signalCEready() Informs FeeServer that initialization has been finished the termination of this thread is in charge of the CE the init - thread has to continue, if „publish()“ has been called.

Interface FeeServer  Control Engine Status of InterCommunication on FeeControl int issue(char* command, char** result, int* size) FeeServer relays a command to the CE and retrieves the result of it. command: pointer to the command data (allocated and freed by FeeServer) result: pointer to the pointer where CE stores the result data (allocated by CE, freed by FeeServer) size: when called: size of command, when returning: size of result ,

Interface FeeServer  Control Engine Status of InterCommunication on FeeControl int issue(char* command, char** result, int* size) returns an error code, if call was unsuccessful, else 0 is executed in an own thread to determine if CE is working (Watchdog) thread will be terminated by FeeServer after timeout, if CE gets stuck ,

Interface FeeServer  Control Engine , Status of InterCommunication on FeeControl void cleanUpCE() Tells CE to clean up to shut down properly when the FeeServer exits.

Status of InterCommunication on FeeControl , FeeServer init process CE initializeCE() signalCEready() publish(Item*) start server Sequence of Communication (initialization, called once)

Status of InterCommunication on FeeControl , FeeServer command received CE issue(...) return result deliver result to FeeClient Sequence of Communication (serving state, executed n-times) execute Command

Status of InterCommunication on FeeControl , FeeServer exit - command received CE cleanUpCE(...) clean up FeeServer and exit Sequence of Communication (clean up, called once) do the clean up stuff

Status of InterCommunication on FeeControl , Data access on InterComLayer Structure of Database ??? Naming conventions ??? When will it be defined ??? ?