Format console timestamp

Question

Hi, We are facing non-human looking timestamp output in the console:

[ INFO] [1465210897.698024206]: Some log msg

while nicely readable in the log files:

[roslaunch][INFO] 2016-06-06 12:35:22,972: Some other log msg

My rosconsole.conf is found and responds on log-level settings. Unfortunately any attempt to format the console timestamp format fails.

log4j.logger.ros=INFO
log4j.logger.ros.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

How to control this behaviour?

---

Originally posted by langsware on ROS Answers with karma: 31 on 2016-06-06

Post score: 3

---

Original comments

Comment by shoemakerlevy9 on 2017-04-10:
I would greatly appreciate something like this. I use robot upstart which dumps all the rosout lines into a single file. Its really hard to tell when a run took place since all of them get put into the same file.

Answer 1

That's a common request (see this and this question). Doesn't look as if there's an solution, because nobody implemented this yet. If you are willing to contribute, a pull request would probably be appreciated.

P.S.: Personally, I find the "non-human-readable" time format more useful, since that's what's in the message headers and what you get in your code. But this is a matter of personal taste or use case and should be configurable.

---

Originally posted by Martin Günther with karma: 11816 on 2016-06-06

This answer was ACCEPTED on the original site

Post score: 0

---

Original comments

Comment by thinwybk on 2017-10-12:
As long as I do not have to read the log files manually the "non-human-readable" format is ok for me as well. Where is this ROS time format specified and how could I convert it using a Python script to e.g. parse log files?