Get rid of data logger and use rosbag instead.

[GoogleCodeExporter]

It is easy to configure rosbag to log all data with proper timestamps and data 
labels and later parse it with a script to convert it to a text file.

It is not easy to maintain the current data subscriber and publisher to keep 
track of the frequently-changing data fields and update column headers 
appropriately, nor is it easy to update the data parser to reflect said changes.

Rosbag is just one way of making it easier (hopefully) to save and read data.

See this wiki page on the rosbag API: http://www.ros.org/wiki/rosbag/Code%20API

Original issue reported on code.google.com by yoos117@gmail.com on 16 Apr 2012 at 7:37

[GoogleCodeExporter]

Original comment by yoos117@gmail.com on 19 Apr 2012 at 7:10

• Changed state: Accepted

[GoogleCodeExporter]

No longer desired. See Issue 78.

Original comment by yoos117@gmail.com on 22 Jun 2012 at 8:01

• Changed state: WontFix

[GoogleCodeExporter]

Reopened, since roscore does not actually handle the data.

See the explanation of [http://www.ros.org/wiki/Master how roscore works].

Original comment by yoos117@gmail.com on 23 Jun 2012 at 6:06

• Changed state: New

[GoogleCodeExporter]

This is a planned feature for the new Oroception system.

Original comment by jrvanwhy on 17 Jul 2012 at 3:41

• Changed state: Started

[GoogleCodeExporter]

Original comment by yoos117@gmail.com on 17 Sep 2012 at 3:01

• Changed state: Done