<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Pratik Ingle</title>
<link>https://pratik-ingle.github.io/posts/research/index.html</link>
<atom:link href="https://pratik-ingle.github.io/posts/research/index.xml" rel="self" type="application/rss+xml"/>
<description>Plain-language explanations of my research papers and research problems.</description>
<generator>quarto-1.0.37</generator>
<lastBuildDate>Wed, 11 Mar 2026 23:00:00 GMT</lastBuildDate>
<item>
  <title>Scalable Surface-Based Manipulation Through Modularity</title>
  <link>https://pratik-ingle.github.io/posts/research/scalable-surface-based-manipulation/index.html</link>
  <description><![CDATA[ 



<section id="the-problem" class="level2">
<h2 class="anchored" data-anchor-id="the-problem">The problem</h2>
<p>Robotic Manipulation Surfaces (RMS) move objects by deforming the surface they rest on. This makes them attractive for fragile, irregular, or food-like objects, where grasping can damage the item or require a specialized gripper. The difficulty is scale: dense actuator arrays can give fine control, but they become expensive and mechanically complex when the workspace grows.</p>
</section>
<section id="the-core-idea" class="level2">
<h2 class="anchored" data-anchor-id="the-core-idea">The core idea</h2>
<p>The paper asks whether a manipulation surface can be made modular. Instead of building one very dense surface, we connect fabric-based modules and coordinate object movement across module boundaries. Adjacent modules share edge actuators, reducing actuator count from <code>4n^2</code> to <code>(n + 1)^2</code> for an <code>n x n</code> grid.</p>
<p>In a <code>2 x 2</code> prototype, this gives a <code>1 x 1 m</code> workspace with only 9 actuators.</p>
</section>
<section id="what-makes-it-hard" class="level2">
<h2 class="anchored" data-anchor-id="what-makes-it-hard">What makes it hard</h2>
<p>Sharing actuators is efficient, but it mechanically couples neighboring modules. Moving one module can disturb objects on another module. The platform therefore needs both high-level path planning and low-level compensation.</p>
<p>Our framework combines:</p>
<ol type="1">
<li>Manhattan-style conflict-free path planning.</li>
<li>Directional object passing between modules.</li>
<li>A geometric PID controller for positioning.</li>
<li>Compensation strategies for passive-object disturbance.</li>
</ol>
</section>
<section id="result" class="level2">
<h2 class="anchored" data-anchor-id="result">Result</h2>
<p>The system achieves coordinated inter-module transfer and sub-centimeter positioning for heterogeneous objects, including fragile items. Compensation reduced passive-object displacement by 59-78% across the measured configurations.</p>
</section>
<section id="why-i-care-about-this" class="level2">
<h2 class="anchored" data-anchor-id="why-i-care-about-this">Why I care about this</h2>
<p>For me, the interesting part is not only that a surface can move objects. It is that manipulation can be treated as a property of a distributed surface: hardware design, geometry, and control all contribute. That feels like a promising route toward scalable manipulation in logistics, food processing, and other settings where objects are too varied for one gripper.</p>
<p>Paper: <a href="https://arxiv.org/abs/2601.21884">arXiv:2601.21884</a></p>


</section>

 ]]></description>
  <category>research</category>
  <category>soft robotics</category>
  <category>manipulation</category>
  <guid>https://pratik-ingle.github.io/posts/research/scalable-surface-based-manipulation/index.html</guid>
  <pubDate>Wed, 11 Mar 2026 23:00:00 GMT</pubDate>
  <media:content url="https://pratik-ingle.github.io/images/research_view_sketch.svg" medium="image" type="image/svg+xml"/>
</item>
<item>
  <title>Linear Control on a Nonlinear Soft Surface</title>
  <link>https://pratik-ingle.github.io/posts/research/linear-control-nonlinear-soft-surface/index.html</link>
  <description><![CDATA[ 



<p>Soft robotic systems are nonlinear almost by definition: fabrics deform, objects slide and roll, friction changes, and contact geometry matters. It is tempting to assume the controller must also be complex.</p>
<p>Our CASE 2025 paper explores a more pragmatic question: how far can a simple linear controller go on a nonlinear soft manipulation surface?</p>
<section id="why-simple-control-is-worth-testing" class="level2">
<h2 class="anchored" data-anchor-id="why-simple-control-is-worth-testing">Why simple control is worth testing</h2>
<p>Simple controllers are easier to tune, debug, and deploy. When hardware is new, a controller that reveals the important system behavior can be more useful than an opaque controller that only works in a narrow setup.</p>
<p>The goal was not to claim that the surface is linear. It was to test whether a linear controller can still produce useful manipulation when the actuation and object response are nonlinear.</p>
</section>
<section id="the-manipulation-loop" class="level2">
<h2 class="anchored" data-anchor-id="the-manipulation-loop">The manipulation loop</h2>
<p>At a high level, the controller compares the current object position with the target, maps the error into actuator commands, and updates the surface shape. The soft surface then converts those changes into object motion.</p>
<p>The interesting part is that the controller can remain relatively simple while the physical surface performs much of the transformation.</p>
</section>
<section id="takeaway" class="level2">
<h2 class="anchored" data-anchor-id="takeaway">Takeaway</h2>
<p>For grasp-free manipulation, the controller and hardware should be designed together. The surface is not just a passive floor; it is part of the computation.</p>
<p>Paper: <a href="https://doi.org/10.1109/CASE58245.2025.11163787">DOI</a></p>


</section>

 ]]></description>
  <category>research</category>
  <category>control</category>
  <category>soft robotics</category>
  <guid>https://pratik-ingle.github.io/posts/research/linear-control-nonlinear-soft-surface/index.html</guid>
  <pubDate>Sat, 16 Aug 2025 22:00:00 GMT</pubDate>
  <media:content url="https://pratik-ingle.github.io/images/research.svg" medium="image" type="image/svg+xml"/>
</item>
<item>
  <title>Soft Manipulation With Fewer Actuators</title>
  <link>https://pratik-ingle.github.io/posts/research/reduced-actuator-soft-manipulation-surface/index.html</link>
  <description><![CDATA[ 



<p>A common way to build a manipulation surface is to place many actuators under it. That can work, but it makes the platform expensive, mechanically dense, and difficult to scale.</p>
<p>In our RoboSoft 2025 paper, we explored a different design: a soft surface actuated by fewer vertical actuators, spaced far enough apart that the object can be much smaller than the distance between actuators. This creates a control problem because the surface is nonlinear and continuous, but it also creates a hardware opportunity: fewer actuators can cover a larger area.</p>
<section id="what-the-surface-does" class="level2">
<h2 class="anchored" data-anchor-id="what-the-surface-does">What the surface does</h2>
<p>The surface changes shape, and the object moves because gravity, contact geometry, and surface deformation combine into a controllable motion field. The robot does not grasp the object. It changes the world under the object.</p>
</section>
<section id="why-heterogeneous-objects-matter" class="level2">
<h2 class="anchored" data-anchor-id="why-heterogeneous-objects-matter">Why heterogeneous objects matter</h2>
<p>Real applications rarely contain one perfect object. Objects differ in weight, shape, size, fragility, and friction. A manipulation surface should not need a new gripper for every case.</p>
<p>That is why this line of work focuses on heterogeneous objects. The long-term question is whether a single soft surface can provide enough controllability while staying mechanically simple.</p>
</section>
<section id="what-i-learned" class="level2">
<h2 class="anchored" data-anchor-id="what-i-learned">What I learned</h2>
<p>Hardware simplicity moves complexity into modeling, sensing, and control. That tradeoff is not automatically good, but it is interesting: if the surface can be controlled robustly, sparse actuation makes the system much easier to scale.</p>
<p>Paper: <a href="https://doi.org/10.1109/RoboSoft63089.2025.11020841">DOI</a></p>


</section>

 ]]></description>
  <category>research</category>
  <category>soft robotics</category>
  <category>hardware</category>
  <guid>https://pratik-ingle.github.io/posts/research/reduced-actuator-soft-manipulation-surface/index.html</guid>
  <pubDate>Mon, 21 Apr 2025 22:00:00 GMT</pubDate>
  <media:content url="https://pratik-ingle.github.io/images/research_goal_sketch.svg" medium="image" type="image/svg+xml"/>
</item>
</channel>
</rss>
