Portrait of Rushav Dash

Rushav Dash

MS Technology Innovation (Robotics) · University of Washington
BS Mechanical Engineering · University of Washington

I'm building a career in robotics, with a focus on the more novel directions of the field — biomimicry and on-board autonomy.

Previously: OneCourt · Zap Energy · Posner Research Group · Integrated Fabrication Lab · GIX

Projects

Project Roost — image placeholder

Project Roost

In progress

Bio-inspired quadcopter that perches autonomously using on-board machine vision.

  • TBD
Result: TBD
▼ more ▲ less about Project Roost
Sponsor: None (student-led) Team role: Project lead / captain · Mechanical lead · Motion capture lead
Description

Capstone project: a bio-inspired quadcopter that lands and perches on its own. Instead of relying on an off-board system or a pre-surveyed target, the drone finds and evaluates a landing site with machine vision running on its own compute, then executes the approach and landing autonomously. [TODO: confirm scope — target type, platform, and what "perching" means mechanically.]

My contribution
  • Pitched the project and got it approved as a student-led capstone.
  • Assembled the team.
  • Began initial design and research with the team.
Wrist-camera view of the task board in simulation with the target SFP port marked by a red crosshair

Intrinsic AI Challenge

Completed

Solo entry to Intrinsic’s AI for Industry Challenge: teaching a UR5e to insert fiber-optic connectors using only wrist cameras and a force/torque sensor.

  • ROS 2
  • PyTorch
  • ResNet-18
  • ACT / LeRobot
  • Docker
Result: 123/300 on the competition portal · best local run 160.9/300 with two partial insertions
▼ more ▲ less about Intrinsic AI Challenge
Sponsor: Intrinsic (Alphabet) with Google DeepMind — AI for Industry Challenge 2026 Team role: Solo — perception, control, imitation learning, and submission infrastructure
Description

The qualification task puts a UR5e in Gazebo in front of a task board whose position, orientation, and port layout are randomized every run, and asks it to insert SFP and SC fiber-optic connectors using only three wrist cameras, a force/torque sensor, and joint states. Over ten weeks I built the whole stack from zero: per-port ResNet-18 regressors that locate ports in camera pixels, back-projection through the camera intrinsics to a 3D target, and a Cartesian impedance controller that approaches, aligns, and descends with force-modulated step sizes. A parallel imitation-learning track collected 530 demonstrations (169 GB) and trained an ACT policy with LeRobot on an RTX 5090. I did not achieve a full insertion; the gap between "close" and "inserted" on a 14 mm port from pixels alone is the honest headline.

My contribution
  • Trained eight generations of per-port ResNet-18 detectors (four models, one per port) and fixed the biggest score jump of the project by retraining on 360° yaw data, which added roughly 60 points on hard board configurations.
  • Wrote 20+ versions of the classical policy on top of the Cartesian impedance controller, including the force-modulated descent (full step below 5 N, half step 5–10 N, halt above 12 N) and the SFP descent-depth fix that removed a 24-point contact penalty per trial.
  • Built the data-collection recorder, the LeRobot/ACT training track, and a multi-config docker-compose benchmark that exposed detector overfitting; shipped 46+ Docker images to the competition portal under the sensor whitelist.
What I'd do differently

Build the multi-config benchmark on day one instead of tuning against the single sample config my detector had memorized, and use the wrist camera for closed-loop visual servoing during the approach rather than one snapshot from survey height.

Thoth title card: enterprise AI knowledge platform, with the chat UI answering a T-Mobile 5G network question

Project Thoth

Completed

Orchestrator-agent platform for T-Mobile that captures expert knowledge through AI-led interviews and answers only from approved, subject-scoped sources with citations.

  • FastAPI
  • ChromaDB
  • Claude API
  • React
  • RAG
Result: Selected as the team to present to T-Mobile leadership.
▼ more ▲ less about Project Thoth
Sponsor: T-Mobile — GIX × T-Mobile hackathon Team role: Backend, classifier, and benchmark API — team of four
Description

Large companies keep deep expertise in the heads of senior staff, and documenting it is slow and rarely searchable in context. Thoth turns capture into a guided AI interview, storage into a per-subject ChromaDB collection, and retrieval into scoped, grounded answers with mandatory citations. It is an orchestrator, not an answerer: a Claude Haiku 4.5 classifier routes each question by confidence to a subject-scoped Sonnet 4 agent, a clarifying question, or an admin escalation. Knowledge passes a two-stage SME-then-admin approval before it is indexed, and with zero approved entries the query path refuses to call the model at all. Stack: FastAPI, SQLAlchemy + SQLite, ChromaDB, React + Vite + Tailwind.

My contribution
  • Scaffolded the backend (agents, routes, services, models, seed data) and the React frontend, then built the four-role single-window UI and the one-command launcher.
  • Built the /api/v1 benchmark surface for the evaluation harness (query, knowledge, health, system endpoints), per-call token telemetry, session handling, and the benchmark test script.
  • Owned the subject classifier and confidence routing, tightened the SME answering prompts, and wrote the README, architecture, demo, and production-recommendations docs.
What I'd do differently

Put real auth and a persistent session store in from the start: the PoC lets you pick any profile with no login and keeps sessions in a process-local dict, so it cannot run on more than one worker or be shown to anyone outside the demo without a rewrite.

Overhead RealSense view of the bottle shelf, glass, and the two SO-101 gripper arms

Drunky

Completed

Two-armed SO-101 robot bartender: overhead YOLO finds the bottle, a wrist-camera visual-servo loop aligns the grasp, MoveIt 2 plans the motion, and a recorded trajectory pours.

  • ROS 2
  • MoveIt 2
  • YOLO
  • RealSense
  • Visual Servoing
Result: 62.7% success over 480 trials (71.7% top shelf, 53.8% bottom shelf) · ~68 s per arm, ~2 min 15 s for a two-ingredient cocktail
▼ more ▲ less about Drunky
Sponsor: TECHIN 517 (UW GIX course project) Team role: System orchestration, wrist-camera detection, and visual-servo alignment — team of three
Description

Pick a drink from the menu and two SO-101 arms make it: the right arm handles alcohols, the left handles mixers, and each runs six phases (find, go, align, grab, pour, toss) in sequence so they never share the workspace. An overhead RealSense D435 plus an eight-bottle YOLO model gives a coarse 3D bottle pose from the nearest 10% of depth pixels; at standoff a wrist-camera YOLO drives a proportional visual-servo loop to center the bottle before a TF-computed grasp, and MoveIt 2 plans the collision-aware motion. The team first trained an end-to-end ACT/LeRobot policy, which learned to grab and pour but failed unpredictably with no way to inspect a bad rollout, and pivoted to this explicit per-stage pipeline.

My contribution
  • System orchestration: sequenced the six phases (find, go, align, grab, pour, toss) per arm and the right-then-left hand-off between arms, with a stop-after-stage switch for step-by-step bring-up.
  • Wrist-camera detection and visual-servo alignment: a stock COCO YOLO on each wrist camera that accepts bottle or vase and locks onto the largest box, driving a proportional loop on shoulder pan until the bottle is centered before the grasp.
  • End-to-end tuning of the full pipeline through the 480-trial evaluation: standoff distance, per-shelf grasp offsets, gripper-axis approach, gravity-sag compensation, and retry-then-continue on the pour and toss.
What I'd do differently

Fix the occluded bottom-shelf case, which drags success from 71.7% to 53.8%: about 45% of failures are detection or alignment loss, so a second overhead vantage or a shelf redesign would pay off more than further controller tuning.

Render of the ShoeHugger shell: a translucent grey body with amber spine LEDs, a long snout, and folding wings

ShoeHugger

Completed

Autonomous TurtleBot3 that locks onto your feet with YOLOv8 pose keypoints, follows you between rooms, and flaps motorized wings in Attack or Stalk mode.

  • ROS 2
  • YOLOv8
  • Nav2
  • SLAM
  • Dynamixel
Result: Live multi-room demo with both behavior modes; the full ROS 2 stack and control UI launch from a single command
▼ more ▲ less about ShoeHugger
Sponsor: University of Washington GIX — TECHIN 516 final project Team role: Autonomy lead — team of three
Description

The TECHIN 516 brief asked for a robot that navigates dynamic indoor spaces and interacts with people; we wanted ours to have personality. ShoeHugger is a modified TurtleBot3 Waffle that detects a person with YOLOv8n-pose, tracks their ankle keypoints through an EMA-smoothed lock, and follows at a set distance while a three-zone LiDAR guard (stop, slow, nominal) keeps it safe. SLAM localization and Nav2 planning run underneath, a custom TF broadcast exposes the person frame, and a third Dynamixel drives a four-bar wing linkage for the Attack and Stalk behaviors. Everything, including the Tkinter control UI, comes up from one launch script.

My contribution
  • Built the person-following perception: YOLOv8n-pose ankle-keypoint tracking at imgsz 256 with an EMA-tracked lock so the foot target stays stable through occlusion.
  • Integrated SLAM, Nav2, and a custom TF tree, and wrote the three-zone LiDAR obstacle logic that governs stop, slow-down, and nominal following.
  • Designed the Attack/Stalk state machine, the Tkinter control UI over ROS topics, and the single-command launch orchestration for the whole stack.
What I'd do differently

Actually use the map. SLAM only draws the RViz view; following and avoidance are purely reactive on the LiDAR, so a lost person means spinning in place to search. Planning on the live map would let it re-acquire someone around a corner instead of guessing.

CAD render of the VitreaClear transducer rod assembly with exploded and sectioned views

VitreaClear

Completed

Non-invasive ultrasound device that uses acoustic radiation force to push vitreous floaters out of the visual axis, as an alternative to vitrectomy surgery.

  • SolidWorks
  • Transducer Design
  • Closed-loop Control
  • MATLAB
  • Python
Result: Patent pending · externally funded · finalist, UW Hollomon Health Innovation Challenge
▼ more ▲ less about VitreaClear
Sponsor: Scott Lipsky, Seattle entrepreneur Team role: Project lead
Description

Eye floaters affect millions of people, and the only current treatment, vitrectomy, is invasive surgery that risks retinal detachment and cataract progression. VitreaClear applies focused ultrasound from outside the eye so that acoustic radiation force displaces floaters out of the visual axis. We characterized transducer beam profiles to set a focal geometry that targets the vitreous chamber without crossing the retinal plane, validated therapeutic parameters (geometry, drive amplitude, pulse duration) over dozens of water-bath runs, and built a real-time closed-loop power controller to hold acoustic output steady across trials.

My contribution
  • Led transducer system design: beam-profile characterization and focal-geometry optimization for the vitreous chamber.
  • Developed the real-time closed-loop power controller and the Python/MATLAB signal-processing layer that closes the loop.
  • Ran the iterative water-bath validation campaign and assembled the bench prototype.
What I'd do differently

Build the closed-loop power controller and data logging before the parameter sweeps, not after. We tuned focal geometry, drive amplitude, and pulse duration over dozens of water-bath runs without steady acoustic output, so the early runs are not directly comparable to the later ones.

Experience

OneCourt
Production Tech Intern
Jun 2026 – Present
  • Refurbished eight retired units into a demo fleet and onboarded every device to the latest software architecture.
  • Wrote battery and charger spec sheets for the manufacturing partner for EV1 prototype sourcing, plus PCB packaging procedures, build schedules, and device validation docs.
  • Set up a vibration test bench, pursued ESD safety certification for production devices, and soldered 128-motor arrays onto direct-to-consumer builds.
  • Battery Systems
  • PCB Assembly
  • ESD Safety
  • Raspberry Pi
Zap Energy
R&D Engineering Intern
Jul – Aug 2023 · Jun – Aug 2024
  • Designed a ±10 µm precision fuel-injection system for fusion reactor prototypes: SolidWorks, GD&T, thermal FEA at 200 °C, 5-axis CNC.
  • Built an Arduino-controlled thermal cycling system holding ±0.5 °C at 250 °C with PID, solid-state relays, and a custom PCB with hardware safety interlocks.
  • Built a 26 kN high-speed force test rig (custom DAQ, signal conditioning, K-type thermocouples, LabVIEW) and automated stress-strain analysis in Python, cutting component evaluation time by 40%.
  • SolidWorks
  • GD&T
  • FEA
  • DAQ Systems
Global Innovation Exchange, UW
Prototype Lab Assistant
Dec 2025 – Present
  • Beta-tested the full robotics curriculum (SLAM, LiDAR, YOLO, sensor fusion, waypoint navigation) ahead of 70+ graduate students.
  • Support students with FDM/SLA printing and PCB cutting for robotics projects, and troubleshoot mechanical assemblies and electronics integration.
  • ROS 2
  • 3D Printing (FDM/SLA)
  • SLAM
  • Electronics Integration
Posner Research Group, UW
Research Lab Assistant
Apr – Aug 2024
  • Fabricated a biomimetic artificial finger with strain-gauge arrays for robotic tactile sensing using 6 µm silicone molding.
  • Reached 2 µm repeatability and 0.1 N force resolution through iterative FEA and calibrated signal processing.
  • Biomimetics
  • Silicone Molding
  • FEA
  • Signal Processing
All skills
Mechanical · SolidWorks · Fusion 360 · FEA · GD&T · Transducer Design · Battery Systems
Electrical · PCB Design · PCB Assembly · Soldering · Arduino · Raspberry Pi · DAQ Systems · Sensor Integration · ESD Safety
Software · Python · C++ · MATLAB · ROS 2 · Nav2 · SLAM · MoveIt 2 · OpenCV · YOLO · PyTorch · Docker · Linux · Git
Fabrication · 3D Printing (FDM/SLA) · Laser Cutting · 5-axis CNC · Silicone Molding · PCB Cutting

Contact

Open to robotics and mechatronics roles — available April 2027