Assuming 'good faith' when responding almost always works better even if the original response was not in fact in good faith. Assuming good faith gives the benefit of the doubt to those trying to help you, avoiding: insulting well meaning community members, and poisoning the mood. You are most likely to get a good answer if you provide a Short, Self Contained, Correct (Compilable) Example or a Minimal, Complete, and Verifiable example Īssume ' good faith': It's easy to mis-interpret the meaning or tone of comments on the internet. To make your code snippets and error messages better readable, format them correctly (mark the code and press Ctrl-k). You must tag at least the rosdistro version. Always tag your questions appropriately.Screenshots or movies to demonstrate the problem. Bag files and code samples that can reproduce the problem.Ogre.log for rviz, if possible (run with rviz -l) ROS environment variables ( env | grep ROS) When discussing any compiling/linking/installation issues, also provide:.Text in the screenshot images is not searchable (e.g. Instead, cut/copy and paste whenever you can. Please DO NOT post a screenshot of the terminal or source file. Small typing mistakes can make a large difference and time wasted. Cut and paste them directly from the terminal window to which they were printed. "I'm running OS X 10.5 on an iBook," or "I'm running Ubuntu Karmic on an x86, with kernel 2.6.31." For Linux, always provide the distro and kernel versions.Īny warnings or errors. Your platform (architecture, OS & version/distro). "I'm using ROS C Turtle with pr2_simulator 1.1.1 and vocabulary_tree r30294" Names and versions of stacks/packages that you're using.
0 Comments
Leave a Reply. |