Skip to main content

AVxcelerate Simulation Framework 2025 R2 SP02

Class Hierarchy

Last update: 19.09.2025

Go to the graphical class hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 123]
 Csimulation_framework::core::IEvaluator< osi3::GroundTruth >
 Csimulation_framework::evaluator::GtBaseEvaluatorThis is the implementation of IEvaluator interface and provides users ability to evaluate KPIs that are added by themselves. This class controls all KPIs centrally and fill/reset the KpiMessage accordingly based on each KPI's calculation result
 Csimulation_framework::core::kpi::IKpi< osi3::GroundTruth >
 Csimulation_framework::evaluator::DistanceDrivenEvaluatorClass DistanceDrivenEvaluator
 Csimulation_framework::evaluator::MinTtcEvaluatorClass MinTtcEvaluator
 Csimulation_framework::evaluator::PredictiveMinTtcEvaluatorClass PredictiveMinTtcEvaluator
 Csimulation_framework::autonomy::cli::CliProviderProvides a command-line interface for simulation execution via dependency injection
 Csimulation_framework::autonomy::ISimInstanceCreatorDefines a generic interface for creating instances of core::lifecycle::ISimulationInstance
 Csimulation_framework::autonomy::AutonomySimInstanceCreatorCreates simulation instances specific to autonomy simulation
 Csimulation_framework::core::CliHandles the decision to start the simulation framework
 Csimulation_framework::core::CliParserCommand-line argument parser for simulation framework
 Csimulation_framework::core::IEvaluator< T >Class IEvaluator
 Csimulation_framework::core::ISimfwkCliServerClass ISimfwkCliServer
 Csimulation_framework::core::SimfwkCliServerClass SimfwkCliServer
 Csimulation_framework::core::ISimRunnerInterface for controlling and managing simulation execution
 Csimulation_framework::core::SimRunnerSimulation runner with external control logic
 Csimulation_framework::core::IStandaloneActivityCreatorThis is the interface class for creating a standalone activity service. It defines how a customized activity needs to be instantiated through or not through StandaloneInitData
 Csimulation_framework::core::ITopic
 Csimulation_framework::core::Topic< TopicMsgType >This is the concrete Topic class that can be used for creation of a communication channel with given underlying message. As default type, DDS type will be applied. TopicId is globally unique and represents one single Topic. Different Topics can hold same underlying message type but they are different topics for communication
 Csimulation_framework::core::kpi::IKpi< T >Represents core KPI calculation logic
 Csimulation_framework::core::kpi::IKpiMessageConverterInterface for converting KPI messages between different formats
 Csimulation_framework::core::kpi::KpiMessageConverterClass KpiMessageConverter
 Csimulation_framework::core::kpi::KpiContentStruct KpiContent
 Csimulation_framework::core::lifecycle::FmuConfigA helper struct to pass necessary information to create FmuBaseActivity
 Csimulation_framework::core::lifecycle::IActivityInterface for simulation activities
 Csimulation_framework::core::lifecycle::BaseActivityThis is the basic implementation of IActivity interface. Inheriting classes, i.e. a concrete simulation activity, should implement their logic in ExecuteStep() and add needed pub/sub in AddPublisherAndSubscriber() method
 Csimulation_framework::core::lifecycle::FmuBaseActivityAn activity that subscribes to messages to input to an FMU and publishes the FMU output
 Csimulation_framework::core::lifecycle::IActivityFactoryInterface for creating simulation activities
 Csimulation_framework::autonomy::ActivityFactoryFactory class for creating activities for autonomy simulation
 Csimulation_framework::core::lifecycle::IFmuLogicThe interface for FMU Logic to be used by an FMU activity
 Csimulation_framework::core::lifecycle::FmuLogicAn implementation of the IFmuLogic interface using the FMI4cpp library
 Csimulation_framework::core::lifecycle::ISimulationInstanceClass ISimulationInstance
 Csimulation_framework::core::lifecycle::SimulationInstanceClass SimulationInstance
 Csimulation_framework::core::logging::ILoggerAn interface for implementing custom logging mechanisms
 Csimulation_framework::core::logging::ConsoleLoggerA basic implementation of the logger which logs to stdout/stderr
 Csimulation_framework::core::logging::LoggingInstanceA singleton class to be used for all logging purposes. It can be used to register additional loggers based on the ILogger class to introduce additional logging mechanisms. By default a ConsoleLogger will be registered with each new LoggingInstance. If logging to console is not desired in your use case, you can call ClearLoggers() before adding your custom loggers to disable console logging
 Csimulation_framework::core::SimulationParametersThe SimulationParameters struct encapsulates parameters related to simfwk-core configuration
 Csimulation_framework::core::StandaloneActivityServiceIt provides a running process of desired activity returned by interface IStandaloneActivityCreator and keeps it communicating and being scheduled by simulation framework core process
 Csimulation_framework::core::StateFeedbackRepresents feedback for the execution status of a control command
 Csimulation_framework::core::time::IClockInterface for managing and manipulating simulation time
 Csimulation_framework::core::time::ClockClass IClock
 Csimulation_framework::core::time::ISimulationCompletionCheckerInterface for determining simulation completion
 Csimulation_framework::autonomy::SimulationCompletionCheckerChecks for the completion status of a simulation
 Csimulation_framework::evaluator::DistanceDrivenCalculatorClass DistanceDrivenCalculator
 Csimulation_framework::evaluator::PredictiveTimeToCollisionCalculatorClass PredictiveTimeToCollisionCalculator
 Csimulation_framework::evaluator::TimeToCollisionCalculatorClass TimeToCollisionCalculator
 Cworld_simulator::IWorldSimulatorThis serves as the interface for a world/groundtruth simulator implementation in simulation framework. It ensures that any third party ground truth generator lib could follow this API definition and thus could be easily used in simulation framework. Interface of scenario should follow ASAM OSI3 standard (https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/specification/index.html)

Connect with Ansys