Release notes for DAQ/HLT-I S/W Release tdaq-02-00-01

General notes from s/w librarian

General info

This is a general DAQ/HLT-I release which is intended to be used for the ATLAS data taking starting from April 2009. It is compatible with LCG56 s/w and offline-15 releases branch. W.r.t. tdaq-02-00-00 it does not contain incompatible API changes, but rebuilding of all user code is required.

Supported platforms, compilers and compatibility

External s/w and run-time environment tuning.

Release distribution

Development environment

Important changes requiring user actions:

Packages and tags used in the release

Changes in packages (in ABC order)

dal

Message Passing Node ID

• Add calculation of the message passing Node ID for message passing resources, which are not applications, i.e.
• the object has to be linked with segment's or resource-set's resources
• one of it's base classes has to be "DFMessagePassingNode" class
• it cannot be casted to "BaseApplication" class
• example: objects of "RobinReadoutModule" class from data-flow schema linked as resources
• Rename unused daq::Application::ROB type to daq::Application::ROBIN to support above application types

Disabled Algorithm

1. Remove obsolete check_parents parameter

2. Implement why_disabled() algorithm in Java

• explicitly disabled resource:
     object 'BCM_ROD_Spare@BCM_ROD_Module' is disabled because
       it is explicitly disabled
  
  
• disabled because of direct parent:
     object 'TRTBarrelC_LTP_BusyChannel_BC0@BusyChannel' is disabled because
       it's parent TRTBarrelC_LTP@LTPModule is disabled because:
         it is explicitly disabled
  
  
• disabled because of chain of parents:
     object 'PixelL12_TIM4_busy@BusyChannel' is disabled because
       it's parent PixelL12_RODBusy@RODBusyModule is disabled because:
         it's parent PixelL12_LTP@LTPModule is disabled because:
           it's parent PixelDisks_LTP@LTPModule is disabled because:
             it's parent PixelL0_LTP@LTPModule is disabled because:
               it's parent PixelLTPi_Global@LTPiModule is disabled because:
                 it's parent RCDPixelTtcCratePitL0@RCD is disabled because:
                   it's parent PixelTtcCrateBLayer@Segment is disabled because:
                     it's parent Pixel@Segment is disabled because:
                       it is explicitly disabled
  
  
• resource-set OR disabling:
     object 'ROS-TIL-LBC-ROL-16@ResourceSetOR' is disabled because
       it is "resource-set-OR" and at least one child TileLaserModule@TileLaserModule is disabled because:
         it's parent TileLaserRCD@RCD is disabled because:
           it is explicitly disabled
  
  
• resource-set AND disabling (dummy example):
     object 'ROBIN-TRT-ECC-03-3@RobinReadoutModule' is disabled because
       it is "resource-set-AND" and all children (2) are disabled:
         [1] component ROL-TRT-ECC-03-341402@RobinDataChannel is disabled because:
           it's parent rod341402_ResourceSet@ResourceSetOR is disabled because:
             it is "resource-set-OR" and at least one child rod341402@TRTROD05Module is disabled because:
               it is explicitly disabled
         [2] component dummy@RobinDataChannel is disabled because:
           it is explicitly disabled

3. Set used disabled and enabled components in Java

4. Multiple configuration objects and user enabling/disabling in Java code

DAQPanel

• --setup_dir <setup_dir>        Directory containing setup scripts [default is $HOME]
•  --db_dir <db_dir>                Directory containing database files [default is $HOME]
• --general_dir <general_dir> Directory used to save/get files [default is $HOME]
  

• General tab: Busy Presenter;
• Mon Advanced: MDA Browser, SFO Display, Det Mask;
• Ctrl Advanced: (De)Activate Automatic Recovery.
  

• Use new DVS script;
  
• Use new RM gui script.
  
  

dccommon

General changes

• ROSConf
  • Add support in ROSConf for networked (ROBIN) readout of ROS data.
  • Add the possibily to use multiple Level2 result handlers (pROSs) in a partition.
    • L2PUs automatically configure to equally load available L2RHs.
    • If a L2RH fail, the L2PUs using it will automatically re-configure to use remaining L2RHs in a balanced way.
• Internal updates and bugfixes.

Package Description

• ROSConf, a class that provide configuration information about the ROSs, ROSEs and Level2 result handlers in the partition.
  Intended for use by L2PU, PSC and SFI.
• TrafficShaping, a class that implements a simple traffic shaping mechanism for use with UDP protocol. The reulation is based on time-outs for ROS requests.
  Intended for use by L2PU and SFI.

dcmessages

Changes since tdaq-02-00-00

ddc

DFM

Introduction

Changes since tdaq-02-00-00

• No major changes since tdaq-02-00-00

dnc

dvs

Changes since tdaq-02-00-00

• The tests have been moved to a new package called dvs_tests
• the java version of dvs_gui display is no longer built. New implementation for the dvs display is available in dvs_gui package. See release notes for dvs_gui package.

Fixes:

• It happened that CLIPS engine was stopped before actually finishing evaluating all rules. At next 'test start' click button, clips engine was restarted and finished execution of rules in memory. Problem fixed.
• signature changed for method: void getTestRuntimeOutput (const char* comp_name, std::string test_host,std::string test_output_name);
• new method to unload harware objects with state marked 'OFF' in the database.
  

dvs_gui

Package to implement display for dvs core

• This application (Qt4 implemetation) is supposed to be the replacement of the java implementation of the dvs display. It should provide the same functionalities as the old dvs_gui.
• New gui is started with:
• dvs_start_gui [database_file] [partition]
         database_file    configuration database (you must specify it unless you have defined TDAQ_DB_DATA
                                  (can be specified relatively to cwd or to TDAQ_DB_PATH)
         partition           selected partition (must specify unless you have defined TDAQ_PARTITION)
  
  
• igui starts the new dvs gui
• It uses QTUtils package.
  
• Options not implemented yet: 
• Interactive session
• New options:
• DVS Output: a separate window will print the dvs output during a test session
• Remove Hardware-OFF : will not load from the database the hardware components that have state set to OFF. The corresponding applications running on these machines will not be loaded neither.
• Online Help is implemented.
• TO DO:
• add progress bar on the main window to show the evolution of the testing session
  

errorRecovery

General changes

• Make it possible for a requester application to handle multiple responder types, e.g., the L2PU can handle nodes of both ROS and LVL2ResultHandler type.
• Internal improvements and bug fixes only.

gatherer

Merged the gatherer and MonGatherer packages.

Removed IS_OH from the schema. Named the binary Gatherer instead of GathererApplication.

Parallelize the gatherer.

Introduced message forwarding.

histmon

General changes

Histograms published with history by default. The history tag is derived from current time & update interval. If original histograms were designed to be LBN aware then LBN is used as a tag.

igui

Introduction

General changes  

• In the Segment & Resource panel, for the indirect disabled items, it is possible to find the reason why a segment or a resource is disabled pressing the middle mouse button with the mouse pointer on the node. An Information Dialog Frame showing the reason is displayed.
  
• If mrs_monitor is started from IGUI button, the user name is added at default logfile name. The logfile can be found at  /tmp/mrs_monitor_username.log
• The online help has been updated.
  

• Fix the behaviour of ELOG interface when the ELOG server is not accessible.
  
• Fix the multiple ELOG dialog window problem.
• Fix the behaviour of Data Set Tags panel at run state change.
  
  

Igui

• A panel to send transition commands to the RootController
• A panel showing run information and settings
• This panel is located just below the one used to send transition commands to the Root Controller. It contains some tabs:
• Information: it shows general information about the run;
• Counters: it shows counters (event, rates, etc) for the current run;
• Settings: here the used can set some run parameters (this tab replaces the RunParams panel in igui).
  
• A panel containing anything to operate the Run Control
• Run Control tree:
  
• Recovery commands are implemented using a pop-up menu; just right click on a controller/application and a contextual menu will appear showing all the commands the user can send.
• In status display mode the user cannot send any command and the contextual menu will not appear.
• Infrastructure panel:
• No changes with respect to igui.
• Advanced panel:
• This sub-panel contains three task panes giving access to some extra functionalities
• FSM transition commands
• This panel gives the possibility to send transition commands to the selected application; only valid commands are shown.
• Advanced commands
• Here the user can sends some extra commands to the selected application: set debug level, and publish state/statistics.
• Application information
• Simple form showing detailed information about the selected application.
  
• A panel to enable or disable segments and resources
• Extra information about the reason why a component is disabled is available via a tooltip or a dialog (shown with a mouse righ button click).
  
• A panel showing MRS log messages
• As in igui this panel is located at the bottom of the main frame, but now this panel is surrounded by two toolbars giving access to some functionalities available before in a separate panel:
• Using the top toolbar the user can select the MRS subscription criteria (to apply the changes the subscribe button at the right side should be pushed);
• Using the bottom toolbar the user can clean the message window, select the message format (short or long), choose the number of visible messages and see the current subscription criteria.
• When this panel owns the focus (usually selecting a message) the CTRL-F keyborad combination will show a find dialog useful to quickly browse the shown messages.
  

l2pu

General changes

l2rh

General changes

• Use time-stamp to garbage collect 'old' entries in the LVL2Result store,specially when the store is full.
• LOG configured state.
• Internal improvements and bug fixes.

ls

Introduction

This package substitues the obsolete logService. A new requirement whereby database technologies other than ORACLE had to be dropped came in around spiring 2007. This new requirement meant the re-writing of the logService package, which was higly dependent on MySQL. This opportunity was taken to refactorize the code, especially the log manager, which was never very user friendly. The database access in C++ is done using the CORAL interface, which hides the underlying technology. For the log manager, JAVA was the language chosen, since it brings in the flexibility requiered to make this tool more intuitive. The resulting java application can be run from the console, or remotely using the Java Web Start technology.

Known issues/bugs

In the Log Manager, when righ-clicking on the Messages Table (right hand side panel) or Partition Table (left hand side panel) a Refresh button pops up. This is used to update the current view of partitions and messages, respectively. Refreshing these objects only works if one right-clicks the mouse without moving it; that is, press and release without changing the X and Y pointer of the mouse. This may be a problem with Java. In the meantime, one can also perform a Refresh via the options in the top menu File: 'Refresh tree' and 'Refresh table'.

To be implemented

Add an option to display statistics, internal and from IS.

Changes from previous release

None

Example applications

Applications

Log Manager

Usage: log_manager 

Instruction on how to use this tool are on the Help menu in the application itself. The Log Manager can also be run using Java Web Start technology from the following link: https://pcatdwww.cern.ch/jnlp/logmanager/logmanager.jnlp A Java application is downloaded and started. You MUST have at least Java 1.6 installed on your local machine.

lsReceiver

Description: This application subscribes to the MRS service to receive and log on a database messages produced by TDAQ applications.

Usage: lsReceiver [-p partition-name] [-u user-name] [-n IS-server-name] [-s threshold-size] -c connect-string [-S subscribe-expression]

Options/Arguments:

        -p partitionName     Partition name

        -u userName          User name

        -n ISserverName      Name of the Information Service to publish the message rate into.

        -c connectionString  Database connection string. 

Test units

logTest

Description: Test binary for the Log Receiver application.

Usage: logTest -c connect-string [-p partition-name] [-l complexity-level]

Options/Arguments:

        -p partitionName      Partition name

        -l level           Level of Complexity of the test [1: open/close - 2: tests the Log Service Infrastructure].

        -c connectionString  Database connection string. 

Utilities

logSelect

Description: Application to retrieve log messages for a given partition according to the search criteria specified. By default, messages are dumped on std::cout.

Usage: logSelect -c connect-string -p partition-name [-i message-name] [-m machine-name] 

                 [-a application-name] [-l time-low] [-u time-up] [-s severity]  

                 [-x text] [-r parameters] [-d order-list] [-e max-rows] [-f offset-row]

Options/Arguments:

        -c connectionString   Database connection string. 

        -p partitionName      Partition name.

        -u userName           User name.

        -n run-number         Run Number.

        -i message-name       Message name or ID.

        -m machine-name       Machine name where the message was issued.

        -a application-name   Application name where the message was issued.

        -L time-low           Lower time threshold (in UTC time).

        -U time-up            Upper time threshold (in UTC time).

        -s severity           Message severity:

                                 0 - SUCCESS

                                 1 - INFORMATION

                                 2 - DEBUG

                                 3 - WARNING

                                 4 - ERROR

                                 5 - FATAL

        -x text               Text in the message body.

        -r parameters         Message parameters.

        -d order-list         Parameter to sort the messages by (MSG_ID, MACHINE_NAME, APPLICATION_NAME, ISSUED_WHEN, SEVERITY, MSG_TEXT, PARAMETERS, RUN_NUMBER).

        -e max-rows           Maximum number of rows to retrieve from the database; 100 by default. If 0, all entries are retrieved.

        -f offset-row         Offset in the table to retrieve the messages from.

logDelete

Description: Application to remove log messages for a given partition according to the search criteria specified.

Usage: logDelete -c connect-string -p partition-name [-i message-name] [-m machine-name] 

                 [-a application-name] [-l time-low] [-u time-up] [-s severity]  

                 [-x text] [-r parameters]

Options/Arguments:

        -c connectionString   Database connection string. 

        -p partitionName      Partition name

        -u userName           User name.

        -n run-number         Run Number.

        -i message-name       Message name or ID.

        -m machine-name       Machine name where the message was issued.

        -a application-name   Application name where the message was issued.

        -L time-low           Lower time threshold (in UTC time).

        -U time-up            Upper time threshold (in UTC time).

        -s severity           Message severity:

                                 0 - SUCCESS

                                 1 - INFORMATION

                                 2 - DEBUG

                                 3 - WARNING

                                 4 - ERROR

                                 5 - FATAL

        -x text               Text in the message body.

        -r parameters         Message parameters.

logGetPartitionNames

Description: Application to retrieve the list of partition names.

Usage: logGetPartitionNames -c connectionString 

Options/Arguments:

        -c connectionString  Database connection string. 

ohp

General changes

To be implemented/known issues:

• Porting to Qt 4

ohpplugins

General changes

Plug-ins list

• Histo Window: Simple Plugins to display histograms in a tab
• Histo Window Tab: A set of Histo Window plug-ins organized in tabs
• Status Window: A penl with the status of OHP and information on active session
• Browser: An extended version of classic OHP browser
• MDI Interface: A desktop to arrange and control the plug-ins
• Histo Window RegExp: A modified version of Histo Window with support for regular expression
• Tile Cosmics: This is a TileCal specific plugin that selects some histograms out of a list to be displayed
• Error: This is a TileCal specific plugin that shows in a table information extracted from histograms
• Legacy Buttons: Reconnect/Stop buttons
• ROOT Interface: Plugin that runs a user defined ROOT macro to handle drawing of histograms

Under Development

• Options Editor: To help modifying histogram drawing options
• Help System: html based help display

oks

OKS Server

• the oks-commit.sh supports directories in addition to files
• add oks-import.sh utility to simplify import of new directories and files
  
• the repository locks remain from abnormally terminated oks commits can be removed on Point-1 by DAQ experts using /oks/admin/unlock-repository.sh script via sudo
• the "Replace" dialog of OKS Data editor proposes user to check-out repository file containing modified objects
• file-related relative pathnames and absolute pathnames includes are not allowed (in particular to avoid inclusion of files stored outside current repository and to simplify consistency check by oks-commit.sh)
  

OKS Performance Improvements

• the OKS library uses pool of threads to load OKS data files, i.e. the data files can be read in parallel
  
• the number of threads by default is equal to number of the computer's CPU cores
• it can be modified via OKS_KERNEL_THREADS_POOL_SIZE environment variable
• the OKS library does not stop reading of files on first error, but continues loading of files in parallel threads until their ends or errors
• thus the final error report may contain several errors coming from different files
• this error report may change between different runs of OKS utilities even if the files were not updated
• for optimal performance it is recommended:
1. to reduce number of schema files (at some point after a schema file parsing OKS requires single active thread to update the database schema)
   
2. to avoid huge data files (processing of single data file is not parallelized since XML files are non indexed)
   

OnlineRecovery

Introduction

RunController expert system

Server

Core functionality

• An application with decision set to RESTART will be restarted up to a maximum of 5 times. After this restarts will not happen and it will be considered an error instead. If the last restart happened more than 30 min ago the counter is reset (it is also reset if the controller goes back to NONE state).
• An application with a failed test will be re-tested up to a maximum of 3 times. After this a failed test is considered an error. If the last retest was more than 10 min ago the counter is reset.
• If specific recovery is defined (through extra rules files) these might override the database settings.
• An application with decision IGNORE will not be ignored if they are depended upon by an application that is running and has membership IN. In this case it is considered and error and an ers message will be sent containing all the applications depending upon it.

Expert system server

• State - if false no recovery is done.Otherwise recovery is performed according to the following settings.
• Ignore Xoff - if true ROS XOff is not taken into account, otherwise recovery is not done if ROS Xoff is the cause of busy ROD.
• Automatic - if false the user is asked before recovery is performed (through IGUI). If true, recovery is done without user input.

Changes since tdaq-02-00-00

• Lvl2 recovery now also in the case of L2SV dying
• Recovery in the case of a failed HLT prescales update
• Disabled RODs are also published in IS using the new DisabledROD IS structure. Information is published in the RunCtrlStatistics IS server.

Known bugs

Utilities

error_viewer 

owl

new features

#include 

PmgGui

• Fixed bug  #46477 (https://savannah.cern.ch/bugs/?46477): "The PMG IS panel in IGUI may show wrong processes on some host".
  

ProcessManager

• Following changes in the system package, now started processes no more inherit the pmgserver initial environment;
  
• Added some additional verbosity interacting wit the AccessManager and the ResourceManager;
• Fixed problem with process stop time publication in IS.
  

RCDLTPModule

Introduction

General changes

• Introduced classes to load the pattern generator from an OKS object in addition to from a file. New classes LTPPattern, LTPPatternFile, LTPDeadtimePattern created. Backward compatibility with tdaq-02-00-00 is ensured.

RCUtils

robin_ppc

RunController

Introduction

This package contains the Run Control for the TDAQ. It provides two C++ interfaces which allow the user to introduce case-specific actions carried out when a command is received: UserRoutines.h and Controllable.h. The two interfaces have completely different purposes!
A developer shall extend from UserRoutines.h only if he is customizing a controller at an intermediate level of the run control tree (i.e. with child applications). He can create UserRoutines objects to be called at the corresponding state-transitions and commands before they are processed by the Controller itself (i.e. transmitted to the children).

A developer of leaf applications (run control applications without children) shall only extend the Controllable.h interface. He creates a Controllable object to be called at the corresponding state-transitions and commands.

API additions since Previous Release

The UserRoutines class has been extended with 2 methods: virtual bool actionEnable(), virtual bool actionDisable(). These methods allow users to specify actions when a command ENABLE/DISABLE is received. The use case is a controller which is also a leaf application dealing with the stopless recovery (pattern which is discouraged since several years but still in use...).

Visible Changes since Previous Release

• Substates are implemented via a new mechanism. Instead of implementing special UserRoutines in a controller, the applications which need extra synchronization points can use "Barrier" class (see details later on).
• The periodic publish and publish statistics commands are dealt with differently. In tdaq-01-09-01 the controller was broadcasting these commands to all children at regular intervals. In order to allow different children to have different publishing frequencies, each leaf application starts 2 threads once the CONFIGURED state is reached: these wake up at the interval specified in the DB (ProbeInterval and FullStatisticsInterval. 0 = means do not launch thread).
  
• It is not possible anymore to ask a controller to start or restart an application when the controller is in a STATE at which that application should not be running (e.g. cannot start a leaf application in BOOTED).
• The SHUTDOWN command is equivalent to EXIT for all controllers except the RootController, who has one more state (NONE).
• It is now possible to test individual objects sending the command TEST_OBJECT <object name> to a controller.
• It is now possible to issue recovery commands also when the Controller is BUSY (STARTAPP, STOPAPP, RESTARTAPP, TEST_OBJECT, TESTHW, TESTPMG, IGNORE).
• A States class has been introduced which defines all FSM States in an enumeration and provides their textual representation (see details later on).
• If the RootController dies, it can now be safely restarted (by launching again setup_daq) even if the system is in RUNNING state.
  
• The RootController can deal with the following extra commands:
• L1UPDATEPRESCALES: dummy place holder for now.
• HLTUPDATEPRESCALES: the root controller receives as arguments the Trigger SuperMaster Key (SMK) and the L1 and HLT Prescale keys; it blocks the main trigger, inserts the new keys and a new LB into the trigger DB, broadcasts to all nodes the user command "HLT_PrescaleUpdate <lumi block> <SMK> <L1Prescale> <HLT Prescale>"; when the command has been carried out completely it releases the main trigger. If a child does not manage to complete the command correctly it is terminated by the expert system.
• LUMIBLOCKINTERVAL: 2 argument sets are possible "TIME <interval in seconds>" "EVENTS <number of events>". The interval at which the LB changes spontaneously can be changed with this command. The default is "TIME 300".
• LUMIBLOCKINCREASE: increase the LB by 1. Optionally a parameter can be passed to ask for an increase bt more than 1.

Internal Changes since Previous Release

• In the Application class the startAt and stopAt parameters are translated to the exact transition at which the process should be launched/stopped
• Several helper methods have been added to the RunController class in order to better factorize the code.
• the BOOT and INITIALIZE transitions are dealt with as normal transitions.
• The TESTPMG and TESTHW are dealt with as normal active commands and not as pseudo-transitions.
  

APIs

States Class

Barriers Class

#include "RunController/Barrier.h"
myMethod() {
  daq::rc::Barrier a(partitionName, appName, subStateA_Name);
  daq::rc::Barrier b(partitionName, appName, subStateB_Name);
  try {
       a.up();
       b.up();
  }
   catch(ers::Issue &e) {
       ers::fatal(e);
       // do something or return;
  }
  // do whatever you need to do; if you encounter a fatal error, and you
  // don't want all other applications to wait forever on you, lower the barrier with a.down()
  // Now wait that the other applications have reached the synchronization point subStateA
  try {
    a.wait(timeout);
  }
  catch (ers::Issue & e) {
    ers::fatal(e);
    // do something or return;
  }
  // continue with what you need to do
  //Now wait that the other applications have reached the synchronization point subStateB

  try {
    b.wait(timeout);
  }
  catch (ers::Issue & e) {
    ers::fatal(e);
    // do something or return;
  }
  // continue with what you need to do
return;
}

Errors

The RunController hardly takes any decisions when errors occurred. Instead, the corresponding error are forwarded to the Expert System (Online Recovery) which takes a decision accordingly. This decision currently depends on the settings defined on the configuration database. Three fields are available to the user to define the behaviour: IfFails, IfDies, IfError. Note on restart: If the option restart is selected for any of these fields and the restart fails repeatedly, it will cause an error instead.

Timeouts

Known issues/bugs

Change of API planned for next major release!

• Controllable.h : The std::string arguments passed to all methods will be substituted by std::vector. In this way user does not need to do the equivalent parsing of the parameters in their code.
• UserRoutines.h : The equivalent substitution of std::string for std::vector will be made. The userAction(..) will be changed to userAction(std::string command, std::vector arguments).

Applications

rc_setup

Description: Binary to start the basic infrastructure needed by the Root Controller.

Options/Arguments:

        -p partition      Name of the IPC partition (default $TDAQ_PARTITION)

        -d database       Name of the database (TDAQ_DB)

        -s segmentname    Name of the segment

        -n controller     Name of the controller

        -R expertSystem   Expert System library name (without the 'lib' prefix or the '.so' extension, followed by the arguments if any.

run_controller

Description: The RunController is a general purpose control entity for the ATLAS Online infrastructure.

Options/Arguments:

        -p partition      Name of the IPC partition (default $TDAQ_PARTITION)

        -P parentname     Name of the parent

        -s segmentname    Name of the segment

        -n controller     Name of the controller

        -u substates      Library with the substates definition. The library name has to be given without the 'lib' prefix nor the '.so' extension.

        -R expertSystem   Expert System library name (without the 'lib' prefix or the '.so' extension, followed by the arguments if any.

rc_test_controller

Description: Test unit for rc_controller binaries.

Options/Arguments:

        -p partition    IPC partition name (default $TDAQ_PARTITION)

        -n controller   Controller names

SFI

Changes since tdaq-02-00-00

• Can now use ROBINs as data sources (a.k.a switch-based ROS mode)

  • The SFI is able to deal with the ROBINs as data-sources now.
    When going though the ROSs, it asks each one of them, if the data for the event builder are to be requested and taken out from the ROS PC, or from the ROBINs directely. It then uses the appropriate nodeIDs in the list of data sources.
    This way, the list of data sources can be composed of a mixture of ROSs and ROBINs.
  • So, the PC- or ROBIN-based readout is not any more a parameter in the SFIConfiguration, but an attribute given by each ROSApplication.

• Comply with the drop of the nameTag from the RawFileName constructor

SFO

Introduction

Changes since tdaq-02-00-01

• Comply with the drop of the nameTag from the RawFileName constructor

system

Changes since tdaq-02-00-00

• Changes in the behavior of Executable::exec(const param_collection &params, const env_collection &envs):
• Now this method uses internally the execve system call; this means that the child process will not inherit the parent environment but it will be started
  with the environment defined in envs;
• Here is a list of methods effected by this change:
• Executable::start(const param_collection &params, const env_collection &envs);
• Executable::pipe_out(const param_collection &params, const env_collection &envs, const File &input_file, const File &output_file, const File &error_file, mode_t perm).
  

training

Introduction

General changes

• RodPanel exercise in the Gui panel chapter has been updated according to the changes in igui package.
  
• test_vme_interface exercise in the Diagnostic Test chapter has been updated according to the solution.
  

wmi

Introduction

New features

• Remove output messages (when convert files) in DQ plug-in.
• Tree implementation use java.
• Compress files which copy to WEB server(use gzip).