Why must I call roslaunch.configure_logging?
In the roslaunch API example, the function roslaunch.configure_logging is called before creating an instance of ROSLaunchParent.
The documentation says about this function only:
scripts using roslaunch MUST call configure_logging
without further explanation.
Now I have the problem, that after calling the function, I do not get anymore output generated by my script (e.g. with rospy.loginfo). When I remove the call, I get all the outputs and also the roslaunch part seems to work without problems.
So my question is: MUST I really call configure_logging. If yes, why? What are the consequences of not calling it?
Asked by Felix Widmaier on 2017-12-20 09:12:50 UTC
Comments
I assume that you're referring to this documentation (source)?
Asked by jayess on 2017-12-20 15:09:07 UTC
Did you try not calling it and seeing what happens?
Asked by jayess on 2017-12-20 15:09:54 UTC
@jayess: Exactly. Yes, I removed the call and everything seems to work well so far. But since the docstring is pretty strongly telling me to use it, I would like to know if there could be some problems I just did not notice yet.
Asked by Felix Widmaier on 2017-12-21 03:09:36 UTC
The logging in ~/.ros/log directory appears to behave exactly the same, with/without configure_logging(). I wonder what it does...
Asked by Magnus on 2020-12-02 12:52:50 UTC