mongodb_log package from mongodb_store repo

mongodb_log mongodb_store mongodb_store_msgs

Package Summary

Tags No category tags.
Version 0.6.0
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version noetic-devel
Last Updated 2023-02-27
Dev Status DEVELOPED
CI status
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.6.0 (2022-09-20)

  • Ensure Python 3 compatibility in mongodb log (#277)
  • update package.xml to format=3 (#269)
  • Contributors: Gal Gorjup, Kei Okada, Nick Hawes

0.5.2 (2019-11-11)

  • back to system mongo
  • Contributors: Ferenc Balint-Benczedi, Nick Hawes, Shingo Kitagawa, Volker Gabler

0.5.1 (2019-06-28)

0.5.0 (2018-12-20)

  • Merge pull request #231 from bbferka/melodic-devel Melodic devel
  • back to system mongo
  • Contributors: Ferenc Balint-Benczedi, Nick Hawes

0.4.5 (2019-06-28)

0.4.3 (2019-04-04)

  • Merge pull request #238 from charlielito/patch-1 Fix typo in log message
  • Fix typo in log message It is subscribe rather than subsribe
  • Contributors: Carlos Andr

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange

mongodb_log package from mongodb_store repo

mongodb_log mongodb_store mongodb_store_msgs

Package Summary

Tags No category tags.
Version 0.1.30
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version hydro-devel
Last Updated 2017-08-31
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.1.30 (2017-06-23)

0.1.29 (2017-06-19)

0.1.28 (2016-11-09)

0.1.27 (2016-11-01)

0.1.26 (2016-10-14)

  • indigo-0.1.25
  • Updating changelogs
  • indigo-0.1.24
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.25 (2016-04-28)

0.1.24 (2016-04-19)

0.1.23 (2016-04-19)

  • Fixed missing namespace for mongodb_log
  • indigo-0.1.22
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.22 (2016-02-23)

0.1.20 (2015-11-11)

0.1.19 (2015-10-28)

0.1.18 (2015-10-28)

0.1.17 (2015-09-01)

0.1.16 (2015-08-04)

  • add option to treat topic name arguments as regular expression
  • add option to specify collection name
  • Contributors: Furushchev

0.1.15 (2015-05-10)

0.1.14 (2015-04-27)

  • Adding install targets for mongodb_log Closes #129
  • Contributors: Christian Dondrup

0.1.13 (2015-04-22)

  • Recheck topics at a fixed interval in order to attempt to resubscribe to topics that were missing at startup. This closes #126.
  • Changed mongodb_log to not wait for topics to be published, instead subscribing to all the other topics
  • Contributors: Nick Hawes, Nils Bore

0.1.12 (2015-02-09)

0.1.11 (2015-02-09)

  • Extended usage output string by new command line options
  • Changed default behaviour back to its former way The \'a\' command line parameter now activates throttling; not specifying it makes the logger log all tf transformations.
  • Added throttling capabilities for high-frequency tf logging Added tf logging throttling capabilities originally introduced in https://github.com/code-iai/ros-mongodb_log. A transform is only logged when either this transform has not been logged before, or when the new version of this transform is sufficiently different from the one logged before. Additional command line parameters can be used to control how throttling is done:
    • `-k <d>`: Cartesian (vectorial) distance (in meters) threshold between the old and the new transform
    • `-l <d>`: Angular diastance (in deg) threshold between the old and the new transform
    • `-g <d>[: At least log every transform every `d]{.title-ref} seconds, even if nothing changed
    • `-a`: Always log, don\'t throttle
  • Contributors: Jan Winkler

0.1.10 (2014-11-23)

0.1.9 (2014-11-18)

  • Use rospy to remove additional arguments when launched via roslaunch
  • Contributors: Nils Bore

0.1.8 (2014-11-11)

0.1.7 (2014-11-09)

0.1.6 (2014-11-06)

0.1.5 (2014-11-05)

0.1.4 (2014-10-29)

0.1.3 (2014-10-21)

0.1.2 (2014-10-20)

0.1.1 (2014-10-17)

0.1.0 (2014-10-16)

  • This adds latched recording and playback to the log and playback nodes. This is the final part of the functionality to close #5
  • Added meta logging to other C++ loggers.
  • Calling on correct document.
  • Building up type processing knowledge.
  • Adding meta information to C++-logged documents.
  • Handlings strings which cannot be treated as UTF-8 as binary.
  • Moved back to processes to test.
  • Debugging ulimit issue.
  • Contributors: Nick Hawes

0.0.5 (2014-10-09)

0.0.4 (2014-09-13)

  • added libssl and libcrypto for ubuntu distros where this is needed due to the static nature of the libmongoclient.a
  • Contributors: Marc Hanheide

0.0.3 (2014-08-18)

  • Renamed rosparams [datacentre_]{.title-ref} to [mongodb_]{.title-ref}. Fixes #69
  • Renamed ros_datacentre to mongodb_store for to fix #69.
  • Contributors: Nick Hawes

0.0.2 (2014-08-07)

  • Dynamically choose MongoDB API Use Connection if using an older mongopy, otherwise use MongoClient.
  • Cleaned up boilerplate in mongodb_log package.xml Removed a bunch of XML comments (that came from the package.xml template) from the package.xml file. Added pymongo as a run dependency.
  • Main process no longer calls init_node. This fixes bugs related to calling init_node multiple times in the same process. Main process now has its own signal handler for shutting down cleanly.
  • Added \'inserted_at\' meta with proper date object to logged data. This added compatibility with message store and also allows native date queries on results.
  • Changes to how meta info is stored.
  • Added boost filesystem for new version of ld.
  • Added mongo dependency
  • More benchmark removal
  • REmoved rrd bits.
  • Removing benchmarking stuff.
  • Restructuring for new repo position.
  • Moved all files into mongodb_log subdirectory for later inclusion in a broader package.
  • Contributors: Alex Bencz, Christian Dondrup, Nick Hawes

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange

mongodb_log package from mongodb_store repo

mongodb_log mongodb_store mongodb_store_msgs

Package Summary

Tags No category tags.
Version 0.1.30
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version hydro-devel
Last Updated 2017-08-31
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.1.30 (2017-06-23)

0.1.29 (2017-06-19)

0.1.28 (2016-11-09)

0.1.27 (2016-11-01)

0.1.26 (2016-10-14)

  • indigo-0.1.25
  • Updating changelogs
  • indigo-0.1.24
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.25 (2016-04-28)

0.1.24 (2016-04-19)

0.1.23 (2016-04-19)

  • Fixed missing namespace for mongodb_log
  • indigo-0.1.22
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.22 (2016-02-23)

0.1.20 (2015-11-11)

0.1.19 (2015-10-28)

0.1.18 (2015-10-28)

0.1.17 (2015-09-01)

0.1.16 (2015-08-04)

  • add option to treat topic name arguments as regular expression
  • add option to specify collection name
  • Contributors: Furushchev

0.1.15 (2015-05-10)

0.1.14 (2015-04-27)

  • Adding install targets for mongodb_log Closes #129
  • Contributors: Christian Dondrup

0.1.13 (2015-04-22)

  • Recheck topics at a fixed interval in order to attempt to resubscribe to topics that were missing at startup. This closes #126.
  • Changed mongodb_log to not wait for topics to be published, instead subscribing to all the other topics
  • Contributors: Nick Hawes, Nils Bore

0.1.12 (2015-02-09)

0.1.11 (2015-02-09)

  • Extended usage output string by new command line options
  • Changed default behaviour back to its former way The \'a\' command line parameter now activates throttling; not specifying it makes the logger log all tf transformations.
  • Added throttling capabilities for high-frequency tf logging Added tf logging throttling capabilities originally introduced in https://github.com/code-iai/ros-mongodb_log. A transform is only logged when either this transform has not been logged before, or when the new version of this transform is sufficiently different from the one logged before. Additional command line parameters can be used to control how throttling is done:
    • `-k <d>`: Cartesian (vectorial) distance (in meters) threshold between the old and the new transform
    • `-l <d>`: Angular diastance (in deg) threshold between the old and the new transform
    • `-g <d>[: At least log every transform every `d]{.title-ref} seconds, even if nothing changed
    • `-a`: Always log, don\'t throttle
  • Contributors: Jan Winkler

0.1.10 (2014-11-23)

0.1.9 (2014-11-18)

  • Use rospy to remove additional arguments when launched via roslaunch
  • Contributors: Nils Bore

0.1.8 (2014-11-11)

0.1.7 (2014-11-09)

0.1.6 (2014-11-06)

0.1.5 (2014-11-05)

0.1.4 (2014-10-29)

0.1.3 (2014-10-21)

0.1.2 (2014-10-20)

0.1.1 (2014-10-17)

0.1.0 (2014-10-16)

  • This adds latched recording and playback to the log and playback nodes. This is the final part of the functionality to close #5
  • Added meta logging to other C++ loggers.
  • Calling on correct document.
  • Building up type processing knowledge.
  • Adding meta information to C++-logged documents.
  • Handlings strings which cannot be treated as UTF-8 as binary.
  • Moved back to processes to test.
  • Debugging ulimit issue.
  • Contributors: Nick Hawes

0.0.5 (2014-10-09)

0.0.4 (2014-09-13)

  • added libssl and libcrypto for ubuntu distros where this is needed due to the static nature of the libmongoclient.a
  • Contributors: Marc Hanheide

0.0.3 (2014-08-18)

  • Renamed rosparams [datacentre_]{.title-ref} to [mongodb_]{.title-ref}. Fixes #69
  • Renamed ros_datacentre to mongodb_store for to fix #69.
  • Contributors: Nick Hawes

0.0.2 (2014-08-07)

  • Dynamically choose MongoDB API Use Connection if using an older mongopy, otherwise use MongoClient.
  • Cleaned up boilerplate in mongodb_log package.xml Removed a bunch of XML comments (that came from the package.xml template) from the package.xml file. Added pymongo as a run dependency.
  • Main process no longer calls init_node. This fixes bugs related to calling init_node multiple times in the same process. Main process now has its own signal handler for shutting down cleanly.
  • Added \'inserted_at\' meta with proper date object to logged data. This added compatibility with message store and also allows native date queries on results.
  • Changes to how meta info is stored.
  • Added boost filesystem for new version of ld.
  • Added mongo dependency
  • More benchmark removal
  • REmoved rrd bits.
  • Removing benchmarking stuff.
  • Restructuring for new repo position.
  • Moved all files into mongodb_log subdirectory for later inclusion in a broader package.
  • Contributors: Alex Bencz, Christian Dondrup, Nick Hawes

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange

mongodb_log package from mongodb_store repo

mongodb_log mongodb_store mongodb_store_msgs

Package Summary

Tags No category tags.
Version 0.1.30
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version hydro-devel
Last Updated 2017-08-31
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.1.30 (2017-06-23)

0.1.29 (2017-06-19)

0.1.28 (2016-11-09)

0.1.27 (2016-11-01)

0.1.26 (2016-10-14)

  • indigo-0.1.25
  • Updating changelogs
  • indigo-0.1.24
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.25 (2016-04-28)

0.1.24 (2016-04-19)

0.1.23 (2016-04-19)

  • Fixed missing namespace for mongodb_log
  • indigo-0.1.22
  • updated Changelogs
  • Contributors: Nick Hawes

0.1.22 (2016-02-23)

0.1.20 (2015-11-11)

0.1.19 (2015-10-28)

0.1.18 (2015-10-28)

0.1.17 (2015-09-01)

0.1.16 (2015-08-04)

  • add option to treat topic name arguments as regular expression
  • add option to specify collection name
  • Contributors: Furushchev

0.1.15 (2015-05-10)

0.1.14 (2015-04-27)

  • Adding install targets for mongodb_log Closes #129
  • Contributors: Christian Dondrup

0.1.13 (2015-04-22)

  • Recheck topics at a fixed interval in order to attempt to resubscribe to topics that were missing at startup. This closes #126.
  • Changed mongodb_log to not wait for topics to be published, instead subscribing to all the other topics
  • Contributors: Nick Hawes, Nils Bore

0.1.12 (2015-02-09)

0.1.11 (2015-02-09)

  • Extended usage output string by new command line options
  • Changed default behaviour back to its former way The \'a\' command line parameter now activates throttling; not specifying it makes the logger log all tf transformations.
  • Added throttling capabilities for high-frequency tf logging Added tf logging throttling capabilities originally introduced in https://github.com/code-iai/ros-mongodb_log. A transform is only logged when either this transform has not been logged before, or when the new version of this transform is sufficiently different from the one logged before. Additional command line parameters can be used to control how throttling is done:
    • `-k <d>`: Cartesian (vectorial) distance (in meters) threshold between the old and the new transform
    • `-l <d>`: Angular diastance (in deg) threshold between the old and the new transform
    • `-g <d>[: At least log every transform every `d]{.title-ref} seconds, even if nothing changed
    • `-a`: Always log, don\'t throttle
  • Contributors: Jan Winkler

0.1.10 (2014-11-23)

0.1.9 (2014-11-18)

  • Use rospy to remove additional arguments when launched via roslaunch
  • Contributors: Nils Bore

0.1.8 (2014-11-11)

0.1.7 (2014-11-09)

0.1.6 (2014-11-06)

0.1.5 (2014-11-05)

0.1.4 (2014-10-29)

0.1.3 (2014-10-21)

0.1.2 (2014-10-20)

0.1.1 (2014-10-17)

0.1.0 (2014-10-16)

  • This adds latched recording and playback to the log and playback nodes. This is the final part of the functionality to close #5
  • Added meta logging to other C++ loggers.
  • Calling on correct document.
  • Building up type processing knowledge.
  • Adding meta information to C++-logged documents.
  • Handlings strings which cannot be treated as UTF-8 as binary.
  • Moved back to processes to test.
  • Debugging ulimit issue.
  • Contributors: Nick Hawes

0.0.5 (2014-10-09)

0.0.4 (2014-09-13)

  • added libssl and libcrypto for ubuntu distros where this is needed due to the static nature of the libmongoclient.a
  • Contributors: Marc Hanheide

0.0.3 (2014-08-18)

  • Renamed rosparams [datacentre_]{.title-ref} to [mongodb_]{.title-ref}. Fixes #69
  • Renamed ros_datacentre to mongodb_store for to fix #69.
  • Contributors: Nick Hawes

0.0.2 (2014-08-07)

  • Dynamically choose MongoDB API Use Connection if using an older mongopy, otherwise use MongoClient.
  • Cleaned up boilerplate in mongodb_log package.xml Removed a bunch of XML comments (that came from the package.xml template) from the package.xml file. Added pymongo as a run dependency.
  • Main process no longer calls init_node. This fixes bugs related to calling init_node multiple times in the same process. Main process now has its own signal handler for shutting down cleanly.
  • Added \'inserted_at\' meta with proper date object to logged data. This added compatibility with message store and also allows native date queries on results.
  • Changes to how meta info is stored.
  • Added boost filesystem for new version of ld.
  • Added mongo dependency
  • More benchmark removal
  • REmoved rrd bits.
  • Removing benchmarking stuff.
  • Restructuring for new repo position.
  • Moved all files into mongodb_log subdirectory for later inclusion in a broader package.
  • Contributors: Alex Bencz, Christian Dondrup, Nick Hawes

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 0.4.5
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2019-09-04
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.4.5 (2019-06-28)

0.4.3 (2019-04-04)

  • Merge pull request #238 from charlielito/patch-1 Fix typo in log message
  • Fix typo in log message It is subscribe rather than subsribe
  • Contributors: Carlos Andr

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange

mongodb_log package from mongodb_store repo

mongodb_log mongodb_store mongodb_store_msgs

Package Summary

Tags No category tags.
Version 0.5.2
License GPLv2
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/strands-project/mongodb_store.git
VCS Type git
VCS Version melodic-devel
Last Updated 2023-05-24
Dev Status DEVELOPED
CI status
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The mongodb_log package

Additional Links

Maintainers

  • Marc Hanheide

Authors

  • Tim Niemueller
Generic MongoDB Logging for ROS
===============================

Autonomous mobile robots produce an astonishing amount of run-time
data during their operation. Data is acquired from sensors and
actuator feedback, processed to extract information, and further
refined as the basis for decision making or parameter estimation. In
today's robot systems, this data is typically volatile. It is
generated, used, and disposed right away. However, some of this data
might be useful later, for example to analyze faults or evaluate the
robot's performance. A system is required to store this data as well
as enable efficient and flexible querying mechanisms.

This package contains the relevant pieces to setup this generic
logging for ROS. It features a generic logger written in Python
capable of logging any topic, and loggers written in C++ written for
specific message types which are known to be large in size or to be
transmitted at a high frequency. This is to cope with Python inherent
overhead and processing limits. You might find that for certain
additional topics you need to write custom fast loggers following a
template of the existing loggers. If you do this for publicly
available message types we'd like to hear about it and maybe include
it in a later release. We are also investigating the possibility to
have generic message introspection in C++ for ROS, which would remedy
this problem.
Additionally, this package includes tools to monitor the logging
process and MongoDB and generate graphs using RRDtool.

For the conceptual background please refer to the paper "A Generic
Robot Database and its Application in Fault Analysis and Performance
Evaluation" by Niemueller et al. [1].
For technical information please refer to the project's website [2].
The ROS wiki page gives more details on how to get started on ROS [3].

[1] http://www.fawkesrobotics.org/publications/2012/robodb-iros2012/
[2] http://www.fawkesrobotics.org/projects/mongodb-log/
[3] http://www.ros.org/wiki/mongodb_log



CHANGELOG

Changelog for package mongodb_log

0.5.2 (2019-11-11)

  • back to system mongo
  • Contributors: Ferenc Balint-Benczedi, Nick Hawes, Shingo Kitagawa, Volker Gabler

0.5.1 (2019-06-28)

0.5.0 (2018-12-20)

  • Merge pull request #231 from bbferka/melodic-devel Melodic devel
  • back to system mongo
  • Contributors: Ferenc Balint-Benczedi, Nick Hawes

0.4.5 (2019-06-28)

0.4.3 (2019-04-04)

  • Merge pull request #238 from charlielito/patch-1 Fix typo in log message
  • Fix typo in log message It is subscribe rather than subsribe
  • Contributors: Carlos Andr

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged mongodb_log at Robotics Stack Exchange