FairMQ  1.4.33
C++ Message Queuing Library and Framework
FairMQ Documentation

FairMQ [<img src="https://alfa-ci.gsi.de/shields/badge/license-LGPL--3.0-orange.svg" alt="license"/>](COPYRIGHT) <a href="https://alfa-ci.gsi.de/blue/organizations/jenkins/FairRootGroup%2FFairMQ/branches"><img src="https://alfa-ci.gsi.de/buildStatus/icon?job=FairRootGroup/FairMQ/master" alt="build status"/></a> <a href="https://codecov.io/gh/FairRootGroup/FairMQ/branch/master"><img src="https://codecov.io/gh/FairRootGroup/FairMQ/branch/master/graph/badge.svg" alt="test coverage master branch"/></a> <a href="https://scan.coverity.com/projects/fairrootgroup-fairmq"><img src="https://alfa-ci.gsi.de/shields/coverity/scan/fairrootgroup-fairmq.svg" alt="Coverity Badge"/></a> <a href="https://www.codacy.com/app/dennisklein/FairMQ?utm_source=github.com&utm_medium=referral&utm_content=FairRootGroup/FairMQ&utm_campaign=Badge_Grade"><img src="https://api.codacy.com/project/badge/Grade/6b648d95d68d4c4eae833b84f84d299c" alt="Codacy Badge"/></a>

C++ Message Queuing Library and Framework

Release Version Docs
stable release API, Book
testing dev tag Book

Find all FairMQ releases here.

Introduction

FairMQ is designed to help implementing large-scale data processing workflows needed in next-generation Particle Physics experiments. FairMQ is written in C++ and aims to

  • provide an asynchronous message passing abstraction of different data transport technologies,
  • provide a reasonably efficient data transport service (zero-copy, high throughput),
  • be data format agnostic, and
  • provide basic building blocks that can be used to implement higher level data processing workflows.

The core of FairMQ provides an abstract asynchronous message passing API with scalability protocols inspired by ZeroMQ (e.g. PUSH/PULL, PUB/SUB). FairMQ provides multiple implementations for its API (so-called "transports", e.g. zeromq, shmem and ofi (in development)) to cover a variety of use cases (e.g. inter-thread, inter-process, inter-node communication) and machines (e.g. Ethernet, Infiniband). In addition to this core functionality FairMQ provides a framework for creating "devices" - actors which are communicating through message passing. FairMQ does not only allow the user to use different transport but also to mix them; i.e: A Device can communicate using different transport on different channels at the same time. Device execution is modelled as a simple state machine that shapes the integration points for the user task. Devices also incorporate a plugin system for runtime configuration and control. Next to the provided devices and plugins (e.g. DDS) the user can extend FairMQ by developing his own plugins to integrate his devices with external configuration and control services.

FairMQ has been developed in the context of its mother project FairRoot - a simulation, reconstruction and analysis framework.

Installation from Source

Recommended:

git clone https://github.com/FairRootGroup/FairMQ fairmq_source
cmake -S fairmq_source -B fairmq_build -GNinja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=fairmq_install
cmake --build fairmq_build
cd fairmq_build; ctest -j4; cd ..
cmake --build fairmq_build --target install

Please consult the manpages of your CMake version for more options.

If dependencies are not installed in standard system directories, you can hint the installation location via -DCMAKE_PREFIX_PATH=... or per dependency via -D{DEPENDENCY}_ROOT=.... {DEPENDENCY} can be GTEST, BOOST, FAIRLOGGER, ZEROMQ, OFI, PMIX, ASIO, ASIOFI or DDS (*_ROOT variables can also be environment variables).

Usage

FairMQ ships as a CMake package, so in your CMakeLists.txt you can discover it like this:

find_package(FairMQ)

If FairMQ is not installed in system directories, you can hint the installation:

set(CMAKE_PREFIX_PATH /path/to/FairMQ_install_prefix ${CMAKE_PREFIX_PATH})
find_package(FairMQ)

find_package(FairMQ) will define an imported target FairMQ::FairMQ.

In order to succesfully compile and link against the FairMQ::FairMQ target, you need to discover its public package dependencies:

find_package(FairMQ)
if(FairMQ_FOUND)
foreach(dep IN LISTS FairMQ_PACKAGE_DEPENDENCIES)
if(FairMQ_${dep}_COMPONENTS)
find_package(${dep} ${FairMQ_${dep}_VERSION} COMPONENTS ${FairMQ_${dep}_COMPONENTS})
else()
find_package(${dep} ${FairMQ_${dep}_VERSION})
endif()
endforeach()
endif()

If your project shares a dependency with FairMQ or if you want to omit a certain dependency, you may want to customize the above example code to your needs.

Optionally, you can require certain FairMQ package components and a minimum version:

find_package(FairMQ 1.1.0 COMPONENTS dds_plugin)

When building FairMQ, CMake will print a summary table of all available package components.

Dependencies

Which dependencies are required depends on which components are built.

Supported platforms: Linux and MacOS.

CMake options

On command line:

  • -DDISABLE_COLOR=ON disables coloured console output.
  • -DBUILD_TESTING=OFF disables building of tests.
  • -DBUILD_EXAMPLES=OFF disables building of examples.
  • -DBUILD_OFI_TRANSPORT=ON enables building of the experimental OFI transport.
  • -DBUILD_DDS_PLUGIN=ON enables building of the DDS plugin.
  • -DBUILD_PMIX_PLUGIN=ON enables building of the PMIx plugin.
  • -DBUILD_DOCS=ON enables building of API docs.
  • You can hint non-system installations for dependent packages, see the #installation-from-source section above

After the find_package(FairMQ) call the following CMake variables are defined:

Variable Info
${FairMQ_PACKAGE_DEPENDENCIES} the list of public package dependencies
${FairMQ_Boost_VERSION} the minimum Boost version FairMQ requires
${FairMQ_Boost_COMPONENTS} the list of Boost components FairMQ depends on
${FairMQ_FairLogger_VERSION} the minimum FairLogger version FairMQ requires
${FairMQ_PACKAGE_COMPONENTS} the list of components FairMQ consists of
${FairMQ_#COMPONENT#_FOUND} TRUE if this component was built
${FairMQ_VERSION} the version in format MAJOR.MINOR.PATCH
${FairMQ_GIT_VERSION} the version in the format returned by git describe --tags --dirty --match "v*"
${FairMQ_PREFIX} the actual installation prefix
${FairMQ_BINDIR} the installation bin directory
${FairMQ_INCDIR} the installation include directory
${FairMQ_LIBDIR} the installation lib directory
${FairMQ_DATADIR} the installation data directory (../share/fairmq)
${FairMQ_CMAKEMODDIR} the installation directory of shipped CMake find modules
${FairMQ_CXX_STANDARD_REQUIRED} the value of CMAKE_CXX_STANDARD_REQUIRED at build-time
${FairMQ_CXX_STANDARD} the value of CMAKE_CXX_STANDARD at build-time
${FairMQ_CXX_EXTENSIONS} the values of CMAKE_CXX_EXTENSIONS at build-time
${FairMQ_BUILD_TYPE} the value of CMAKE_BUILD_TYPE at build-time
${FairMQ_CXX_FLAGS} the values of CMAKE_CXX_FLAGS and CMAKE_CXX_FLAGS_${CMAKE_BUILD_TYPE} at build-time

Documentation

  1. Device
    1. Topology
    2. Communication Patterns
    3. State Machine
    4. Multiple devices in the same process
  2. Transport Interface
    1. Message
      1. Ownership
    2. Channel
    3. Poller
  3. Configuration
    1. Device Configuration
    2. Communication Channels Configuration
      1. JSON Parser
      2. SuboptParser
    3. Introspection
  4. Development
    1. Testing
  5. Logging
    1. Log severity
    2. Log verbosity
    3. Color for console output
    4. File output
    5. Custom sinks
  6. Examples
  7. Plugins
    1. Usage
    2. Development
    3. Provided Plugins
      1. DDS
      2. PMIx
  8. Controller SDK

privacy