Changes between Version 4 and Version 5 of Software/dOML/CollectingMeasurements
- Timestamp:
- Nov 26, 2007, 1:03:53 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Software/dOML/CollectingMeasurements
v4 v5 1 = Under Modification =2 3 This page is being updated, and is currently not available.4 5 6 1 [[TOC(heading=Tutorial TOC, Tutorial, depth=2)]] 7 2 [wiki:Tutorial Back] … … 20 15 There are two alternative methods for the user to implement this ''interface'' between their experimental applications and the OML Collection Clients. These two alternative methods are: 21 16 22 * Method based on dynamic OML client library 17 * '''Method based on dynamic OML client library''' [[BR]] This method is the appropriate one for experimenters who write their own experimental application in C or C++. 18 19 * '''Method based on OML client daemon''' [[BR]] This method is the appropriate one for experimenters who use existing applciations with no access to their source code, or who develop their own experimental applications in another language than C/C++. [[BR]] '''-- NOTE:''' this method is currently under development, and will be available soon '''--''' 20 21 [[BR]] 22 [[BR]] 23 24 == 1. Interface using OML Client Dynamic Library == 25 26 This method assumes that the experimenter is developing its own experimental application(s) in C or C++. This method is illustrated in figure 2. 27 28 [[Image(OML-Library-Method.png)]] 29 [[BR]] Figure 1. Interface Application/OML Client using Dynamic Library 30 [[BR]] 23 31 24 32 25 * Method based on OML client daemon26 27 28 basedand to define the requested measurement points and parameters. These methods and measurement definitions will be presented in details later in this tutorial.29 30 31 The details and "How-To" of such association will be presented in a following part of this tutorial. In the context of this introduction to the testbed, the client-side measurement collection can be viewed as follows. The application will forward any required measurements or outputs to the OML collection client. This OML client will optionally apply some filter/processing to these measurements/outputs, and then sends them to the OML Collection Server (currently over one multicast channel per experiment for logical segregation of data and for scalability)32 33 There are two alternative methods for the user to interface their experimental applications with the OML Collection Clients and to define the requested measurement points and parameters. These methods and measurement definitions will be presented in details later in this tutorial.34 33 35 34 , and, as such, has a client application programming interface (API). A developer can use this client API through a web interface to define the measurement points and parameters for his or her application. Measurement points and their frequency of collection are an important part of ones experimental plan.