oswinso

Results 58 issues of oswinso

For a while now our firmware code has been very poorly written and pretty much neglected. We need much better lower level controls, and to do that we need better...

level ➤ medium
Epic
type ➤ refactor
area ➤ firmware

With organized pointclouds, another useful visualization for debugging / demo would be a [range image](http://pointclouds.org/documentation/tutorials/range_image_visualization.php#range-image-visualization). I think we should be able to use the rviz image plugin as a reference,...

type ➤ new feature
area ➤ rviz plugin
area ➤ computer vision
level ➤ hard
New members 👍🏻

The ramp in simulation has **white** lines, even though the line detector detects **purple** lines. AC: Create a simulation version of the ramp that has purple lines so that the...

type ➤ bug
area ➤ computer vision
area ➤ gazebo

One of IGVC's biggest goals has been implementing SLAM for our codebase. This year, let's try to get this to work.

type ➤ new feature
area ➤ mapping
level ➤ hard
Epic
type ➤ research
type ➤ design document
area ➤ localization

Currently, the only "metric" we have for our codebase is our CI tests for code compiling and the tests passing. Another metric I want to add is code coverage (even...

type ➤ new feature
github
level ➤ medium

We should come up with a solution to having to pass the same parameter (ie. axle length) to multiple nodes, so that if we do change the axle length at...

type ➤ structural

The `organize_cloud`option is able in the master branch of the [velodyne package]() https://github.com/ros-drivers/velodyne/blob/720829573076bf7d7edd4b1de344924fad909049/velodyne_pointcloud/src/conversions/transform.cc#L49-L54 but not in the latest released version. Having the an [organized cloud](http://pointclouds.org/documentation/tutorials/basic_structures.php) will allow for more efficient...

type ➤ new feature
area ➤ computer vision
level ➤ easy

Currently, we have a giant RequestMessage and ResponseMessage that contains everything. I think we should break out and group the individual messages so that it's easier to manage, ie. ```proto...

type ➤ structural
level ➤ medium
Epic

Currently, we have a giant RequestMessage and ResponseMessage that contains everything. I think we should break out and group the individual messages so that it's easier to manage, ie. ```proto...

type ➤ structural
level ➤ medium

~~Depends on #383.~~ Currently, when lines are hidden as barrels, the mapper will think that there aren't any lines, and thus mark them as empty space. Depends on #536 AC:...

type ➤ new feature
area ➤ mapping