Kyle Stachowicz

Results 40 issues of Kyle Stachowicz

## Description There are some parameters, like world/robot parameters, that need to be stored globally. Some examples are listed: - Robot motion parameters (max linear/angular velocity and acceleration) - Kick...

status / new
status / need-triage
type / new feature

## Description Rewrite the GUI (`soccer`) so that it only communicates with the autonomy/gameplay systems using ROS. We will likely rewrite in Python, which will allow us to more easily...

area / soccer
priority / high
exp / master (4)
Epic

# Description Everywhere where we use a "kick strength" from 0-255 should be removed in favor of a kick speed in m/s. The translation should happen in firmware. Similarly, we...

status / new
status / need-triage
type / new feature

## Description We are removing the ball placement feature as a part of the port to ROS. This will need to be redesigned and reimplemented into the architecture. In the...

status / new
status / need-triage
type / new feature

Pull request: https://github.com/RoboJackets/robocup-software/pull/1554 Link to TODO, or file number/line: https://github.com/RoboJackets/robocup-software/pull/1554/files#diff-20e97f22ce16c3d8e5a213d837353c7eR537 - [ ] Display referee info - [ ] Display whether referee is connected

exp / novice (1)
priority / low
pull request todo

## Description Port the spin kick watcher to the new ROS referee. This was not possible as of #1554 as it requires the vision filter, but as soon as #1555...

status / new
status / need-triage
type / new feature

## Description Many components in our Geometry2d are horifically unoptimized. As part of the motion planning rewrite I've had to fix a few of them. Some examples: - `ShapeSet` collision...

area / support
exp / adept (2)
priority / low
type / enhancement

# Description When we move to the ROS parameter system, we should make sure we have a way to ensure all parameters are used at some point in time (and...

area / soccer
exp / expert (3)
priority / low
type / new feature

Pull request: #1497 Link to TODO, or file number/line: CollectPlanner.cpp:204, SettlePlanner:207

exp / novice (1)
priority / low
pull request todo

## Description In the current iteration of the motion planning rewrite PR set, angle planning (in #1496) creates angular paths that are inconsistent with our current heading and angular velocity....

area / planning-motion
type / new feature
pull request todo