<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Manvel Avetisian — Applied Robotics Researcher</title>
    <link>https://manvel-robotics.com/</link>
    <description>Recent content on Manvel Avetisian — Applied Robotics Researcher</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://manvel-robotics.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Elusive Art of the Corporate Research Lab</title>
      <link>https://manvel-robotics.com/writing/the-elusive-art-of-the-corporate-research-lab/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://manvel-robotics.com/writing/the-elusive-art-of-the-corporate-research-lab/</guid>
      <description>Corporate research labs sound prestigious and look fancy on paper but are often structurally broken in ways nobody talks about openly. I&amp;rsquo;ve managed multiple research teams in these settings and have seen the drama play out countless times. I want to offer a personal, insider perspective from the trenches to cover the problems — and provide some solutions.&#xA;1. Success is ill-defined Let&amp;rsquo;s start with academic research as a counterpart. Academic research has well-defined success metrics: papers, citations, replication.</description>
    </item>
    <item>
      <title>Training and Deploying RL for a $500 Sidewalk Robot</title>
      <link>https://manvel-robotics.com/writing/training-and-deploying-rl-for-a-500usd-sidewalk-robot/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://manvel-robotics.com/writing/training-and-deploying-rl-for-a-500usd-sidewalk-robot/</guid>
      <description>1. Intro: how did the project start? I knew almost nothing about robotics, and that&amp;rsquo;s exactly why I started. After many years in AI and software engineering, I wanted to build something physical.&#xA;During an interview with a self-driving car company, I was surprised to learn how much delivery robots actually cost. Impressive hardware, sensors and AI-capable SOCs pushed the price well above a couple of thousand dollars. I called BS: I was sure I could do that with cheap sensors, cheap compute, or both.</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://manvel-robotics.com/sections/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://manvel-robotics.com/sections/contact/</guid>
      <description> manvel@manvel-robotics.com LinkedIn GitHub Google Scholar </description>
    </item>
    <item>
      <title>Research</title>
      <link>https://manvel-robotics.com/sections/research/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://manvel-robotics.com/sections/research/</guid>
      <description>Experiment 01 — The Deliverator project The Deliverator project investigates using AI to compensate for cheap hardware in autonomous delivery robots. The core question: can lightweight neural networks, running on-device, achieve reliable sidewalk navigation using only basic cameras, consumer-grade IMUs, and standard GPS — bringing total build cost under $500?&#xA;The entire stack is built from scratch by a single researcher: a custom Vulkan-based simulator, an RL training pipeline (SAC on JAX), vision-based navigation, teleoperation, and hardware.</description>
    </item>
  </channel>
</rss>
