Motivation
As a developer, I want to:
Use the acoustics hydrophones to detect the pingers underwater, and send out the various data gathered onto ROS topics.
So that I can:
Use IVC to tell Crush this important information to determine the task order.
Completion criteria
Minimum Viable Product (MVP)
- Topic that tells whether or not Logic/acoustics is ready.
- Topic that tells whether or not the pinger is closer
- Topic that tells the direction of the pinger.
- Service call the supports the gathering of data.
Stretch
- Computed distance to the pinger
- Integration with IVC in task planning (can be separate issue TBD)
Timeline
- Mid to late March
Testing requirements
- Put robot and pinger into water.
- Call ros service and observe data published onto the relevant topics.
Implementation
High-level overview
- Needs a new package.
- Needs new ROS service defined in topic to make a call to existing acoustics code.
- Dump acoustic repo code into ROS package, and edit high level code to pass up data we need.
- Publish data to topics.
Checklist
TBD
Additional notes
N/A
Motivation
As a developer, I want to:
Use the acoustics hydrophones to detect the pingers underwater, and send out the various data gathered onto ROS topics.
So that I can:
Use IVC to tell Crush this important information to determine the task order.
Completion criteria
Minimum Viable Product (MVP)
Stretch
Timeline
Testing requirements
Implementation
High-level overview
Checklist
TBD
Additional notes
N/A