Page 3 of 3
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Sat Dec 07, 2024 3:27 am
by park44
This matches something I went through recently.
OpenVLA is a notable open-source VLA model - roughly 7 billion parameters, trained on hundreds of thousands of real-world robot demonstrations - and has been shown to outperform much larger closed models on some manipulation benchmarks, which says a lot about how much of VLA performance comes from data curation rather than raw scale.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Wed Dec 18, 2024 12:15 am
by ethan_fisc
@park44 To answer this directly:
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed. OpenVLA is a notable open-source VLA model - roughly 7 billion parameters, trained on hundreds of thousands of real-world robot demonstrations - and has been shown to outperform much larger closed models on some manipulation benchmarks, which says a lot about how much of VLA performance comes from data curation rather than raw scale.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Thu Dec 26, 2024 4:11 pm
by dchen
This is exactly the kind of context I was looking for.
'Zero-shot sim-to-real' rarely means literally zero real-world tuning in practice - it usually means the policy transfers well enough to be usable with only calibration and minor safety-limit adjustments, rather than needing a full additional training phase on hardware.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Sat Dec 28, 2024 3:11 pm
by jonathan.rao1
@dchen I'd take that specific number with a grain of salt, honestly.
A lot of what reads as 'full autonomy' in public demos is closer to a mix of scripted state machines, teleoperation for the hardest sub-tasks, and autonomous execution for the easier, well-rehearsed parts - transparency about this mix varies a lot between companies.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Sun Jan 05, 2025 4:40 pm
by deborah59
Same conclusion I've come to. Also worth noting:
Whole-body control (WBC) formulates locomotion and manipulation as a single optimization problem across all joints simultaneously, respecting contact constraints and task priorities - it's more general than ZMP-only approaches but is computationally heavier and harder to tune.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Tue Jan 07, 2025 11:03 am
by mia.weber
@deborah59 This is exactly the kind of context I was looking for.
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Wed Jan 15, 2025 5:11 pm
by servoken70
@mia.weber Yeah, this tracks with what I've read as well.
A lot of what reads as 'full autonomy' in public demos is closer to a mix of scripted state machines, teleoperation for the hardest sub-tasks, and autonomous execution for the easier, well-rehearsed parts - transparency about this mix varies a lot between companies.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Fri Jan 17, 2025 10:12 pm
by mia_lars
@servoken70 I'd take that specific number with a grain of salt, honestly.
Diffusion policies model the distribution of possible actions and sample from it, which handles multimodal manipulation tasks (multiple valid ways to grasp something) more naturally than a single deterministic action output, at the cost of slower inference. Vision-Language-Action (VLA) models like RT-2, OpenVLA, and Physical Intelligence's pi0 unify a vision-language backbone with an action-output head, letting a robot map a camera image and a text instruction directly to motor commands instead of hand-coding separate perception and planning stages.
Re: How do you handle policy versioning and rollback for a deployed fleet?
Posted: Mon Jan 27, 2025 5:45 pm
by pierregreen
Yeah, this tracks with what I've read as well.
Cross-embodiment training (training one policy across data from multiple different robot bodies) has shown some real transfer benefits for high-level behaviors, but low-level control (exact joint torques, timing) still tends to need embodiment-specific fine-tuning.
Makes me wonder how this looks in another five years.