Skip to content
Snippets Groups Projects
Select Git revision
  • 3450df0760f34cbd3597b3f5406ce3d2bc8b1163
  • master default
  • devel
  • topic/perf
  • topic/multipy
  • topic/multipy2
  • topic/soabi
  • v1.5.0
  • v1.4.5
  • v1.4.4
  • v1.4.3
  • v1.4.2
  • v1.4.1
  • v1.4.0
  • 1.3.4
  • v1.3.3
  • v1.3.2
  • v1.3.1
  • 1.3.1
  • v1.3.0
  • v1.2.0
  • v1.0.1
22 results

windows-conda.yml

Blame
  • Forked from Stack Of Tasks / eigenpy
    Source project has a limited visibility.
    debug-doc.h 910 B
    /**
    \page debug Debugging
    
    They are several ways to perform debugging in dynamic-graph depending on your needs or situation:
    - Programmatically inside the entity in C++ will write inside a buffer in a different thread and output in a stream
    (either std::cout or a file). It is detailed in \subpage subp_debug_rt_logger.
    - Programmatically inside the entity in C++ using a member of the entities and the previous real-time mechanism. 
    It provides 4 levels of messags :(DEBUG,INFO, WARNING, ERROR). It is described in details here:
    \subpage subp_logger
    - Programmatically in C++ to avoid overhead with macros and handling level as an int: \subpage subp_dbg_trace
    - If you just need to collect informations from signals (like rosbag). You can use
    an entity called Tracer inside the graph:\subpage tracerdoc . <br>
    A real time version exists
    to write directly inside a memory buffer \subpage tracerrealtimedoc
    **/