Robotics

The uncompensated temperature of the BMP180 is incorrectly converted to a 16-bit signed value, instead of a 32-bit signed value (long). Since the data is 16-bits wide and can therefore not be negative, the easy fix would be to do the following:

sip.js(1128): uncompensated = uint16(data[0], data[1]);

Please see page 15 of the manual of the BMP180 chip:
https://ae-bst.resource.bosch.com/media

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

I'll post it as a question as I am not quite sure that it is a bug. I have been experimenting for a while with the library in a custom environment for a school project and I am really interested in the reproducibility of the result. I have read the disclaimer in the documentation that reads that reproducible results are not guaranteed across multiple platforms or different versions of Pytorch. Ho

From an office hours discussion.. many people have written small gym-like interfaces around Drake. We should provide one in drake master and a tutorial showing how to use it.

Here is the relevant documentation from gym. I'm not worried about the repo name / file structure advice, but simply aim to provide the famil

Ankit Shah and I are trying to use Gen to support a project and would love the addition of a dirichlet distribution

As pointed out in cyberbotics/webots#2787 (comment), we should probably create a common stylesheet.qss in the resources folder that would contain the common style sheets to all platforms.

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"