correlator.cpp File Reference

Implementation of the Correlator class. More...

#include <rtctk/telSub/correlator.hpp>
#include <cassert>
#include <chrono>
#include <optional>
#include <utility>
#include <fastdds/dds/core/LoanableSequence.hpp>
#include <fmt/format.h>
#include <fmt/ostream.h>
#include <taiclock/taiClock.hpp>
#include <rtctk/componentFramework/exceptions.hpp>
#include <rtctk/componentFramework/logger.hpp>
#include <rtctk/telSub/correlatorIf.hpp>

Namespaces
namespace	rtctk
namespace	rtctk::telSub
namespace	rtctk::telSub::CorrelationStatus

Functions
log4cplus::Logger &	GetLogger (const std::string &name="app")
	Get handle to a specific logger.

Detailed Description

Implementation of the Correlator class.

Copyright

SPDX-FileCopyrightText: 2021-2026 European Southern Observatory (ESO)
SPDX-License-Identifier: LGPL-3.0-only

Function Documentation

GetLogger()

log4cplus::Logger & rtctk::componentFramework::GetLogger

(

const std::string &

name = "app"

)

Get handle to a specific logger.

This is used all over the place together with the log4cplus logging macros.

The default logger is retrieved when calling GetLogger() without any further arguments

Instrument RTC developers are supposed to either use:

• the main application logger e.g. GetLogger(), or Getlogger("app")
• custom childloggers of the main application logger e.g. GetLogger("app.foobar")

The RTC Toolkit will use a different logger hierarchy, namely:

• the main rtctk logger e.e. GetLogger("rtctk")
• specific child loggers of the main rtctk logger e.g. GetLogger("rtctk.foobar")

Parameters

name	optional: name of the requested logger

Returns

handle to the requested logger