ros

Feature request

Is your feature request related to a problem? Please describe.
Move test_onboard_logging_generation outside autotest.py to all to validate logger documentation before running the full autotest suite. Ideally, on CI it should run on build_ci.sh with param_parse.py to allow to validate soon that the documentation is correct and not wait that all test pass to trigger a docu

This PR should fix #3435 and also:

• makes Webots display a warning if a Shape with castShadows TRUE contains a mesh geometry which is too large to cast shadows, e.g., the mesh has more than 21845 triangles (21845 = 65535 / 3).
• Fix all the proto files raising this warning.
• Fix all the world files raising this warning.

After testing many worlds, it seems that only the Robo

Just a tip for everyone: I was having trouble running an offline cluster where the Unity Editor was the master and a remote machine was the client. The remote machine was never able to connect to the Editor, but if I ran the standalone build as the master, it connects fine.

Make sure you don't have any blocking Inbound Rules in Windows Firewall with Advanced Security for the Editor version

I recently ran into an issue using AMCL, for which I was given this warning message:

[ WARN] [1425574394.999492201]: No laser scan received (and thus no pose updates 
have been published) for 1425574394.999407 seconds.  Verify that data is being published
on the /scan topic.

However, the actual issue was a miscofiguration of the odom_frame_id :
`<param name="odom_frame_id"