Replies: 3 comments
-
|
Why would you not just want to enable it all the time? What is a use case for this? We do not have 1000Hz topics like in ln that would spam the filesystem otherwise. We do not want to include ln or ROS per default into RAFCON. RAFCON is middleware agnostic! A dedicated middleware would have to be written or adapted (e.g. from the monitoring plugin). Only a strong use case could justify this effort. Originally created by @sebastian-brunner ([email protected]) at 2017-09-29 08:04:14+00:00 (moved from RMC internal repository) |
Beta Was this translation helpful? Give feedback.
-
|
Use case comes from the a typical logging workflow in the labs where we often distinguish between 'setup phase' and 'experiment phase'. During setup, which usually requires countless trials, you don't want/need logs, while during experiments you want logs of potentially multiple middlewares written to a potentially experiment- or trial-specific folder. Imho it would be cool (idea was from @nott-ko ) to have a way to configure and start/stop logging for different middlewares (ROS, LN, Rafcon) with one click or command, e.g. ala This requires some sort of API for the loggers (LN has it already) to dynamically configure at least the output directory and receive a start/stop command. Regarding Rafcon, how these commands are received (LN or ROS service) could be a lightweight plugin, once the functionality is there in form of an internal API-like interface. Default could be a middleware-agnostic, basic UDP based command receiver. Originally created by SebastianRiedela ([email protected]) at 2017-09-29 08:25:25+00:00 (moved from RMC internal repository) |
Beta Was this translation helpful? Give feedback.
-
|
This should be kept in mind when #440 is handled. Originally created by @franzlst ([email protected]) at 2017-12-05 11:58:11+00:00 (moved from RMC internal repository) |
Beta Was this translation helpful? Give feedback.
-
It would be cool to start, stop and configure (e.g. set the storage path) the execution history logging via an API. The API interface could then be made available e.g. using LN / ROS / generel RPC services to configure logging dynamically and remote control it.
Originally created by SebastianRiedela ([email protected]) at 2017-09-18 12:09:31+00:00 (moved from RMC internal repository)
Beta Was this translation helpful? Give feedback.
All reactions