ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial6 min readDisconfirmAI Editorial

Ambarella Technical Marketing Engineer Cicalese: Perception Reports Must Explicitly Retain Position, Time, Uncertainty, and Provenance

Ambarella Technical Marketing Engineer Pietro Antonio Cicalese uses a warehouse robot scenario to argue that information handoffs from perception to coordination must explicitly retain position and extent within a named coordinate frame, capture time with clock reference, multi-dimensional uncertainty, and traceable evidence identifiers; otherwise, the coordinator cannot determine whether two robots are reporting the same obstacle or two different ones.

2026-11-16 14:09 GMT+8

Ambarella Technical Marketing Engineer Pietro Antonio Cicalese proposed a warehouse inspection scenario: one robot reports a fallen cardboard box in Aisle 14, and twenty seconds later, a second robot approaches from the opposite end of the aisle, reporting an obstruction near the entrance. The server now faces an awkward question—are the two robots seeing the same box? If treated as two separate obstacles, it may close more aisles than necessary; if merged into one, it might miss a second, actual obstruction. Cicalese points out that both descriptions can be accurate, yet the coordinator still cannot make a useful distinction.

He argues that the root of the problem lies in how information is handed off from perception to application. The phrase “a fallen box is blocking Aisle 14” is useful for a supervisor glancing at an alert, but for a coordinator comparing reports, it leaves substantial work unresolved: Where along the aisle is the box? How much space does it occupy? Did the second robot see it recently, or did its report spend time waiting for a connection while becoming stale? An accompanying image can help answer some of those questions, provided the recipient can interpret its geometry and capture conditions; a language model may also extract a richer description. But Cicalese emphasizes that neither approach automatically supplies a shared position nor establishes that two observations concern the same object—those relationships need to be represented and evaluated explicitly.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Therefore, the handoff requires an agreed specification between parties: what information is provided, and what behavior is expected when it is incomplete. Software engineers often call this an interface contract. Its value is practical: the receiving application should be able to distinguish a valid position from an unknown one without guessing the sender’s intent. For the warehouse, the report needs to preserve the object’s location and occupied area in a named coordinate frame, with stated units. It also needs the capture time, separate indications of uncertainty across dimensions, and a way to trace the report back to its source observation. A readable summary can sit alongside that structured information for the supervisor to quickly review.

Position conversion itself carries error. Detectors commonly locate the box within a camera image; those pixel coordinates describe where the box appears on the image plane. The coordinator needs a location on the warehouse map, and the conversion requires more than knowing where the robot is standing. A range measurement or a valid geometric constraint (such as a calibrated floor plane) is needed to locate the relevant points in three-dimensional space. The robot’s estimated position and orientation at capture time allow those points to be transformed into the map frame. The box’s extent also needs suitable geometry; the apparent width of its image alone does not establish the space it occupies on the floor.

Cicalese cites the ROS project’s REP 103 standard, noting that inconsistent units and coordinate conventions are precisely what cause integration errors. A camera’s optical frame and a robot’s body frame use different axis orientations; naming the frame and documenting the transformation prevents two components from interpreting the same numbers as different physical locations. Once both robots report in a shared map frame, the server can compare the estimated occupied regions. Overlapping locations and compatible dimensions provide evidence for a common obstacle, but they support an association hypothesis rather than proof of identity. Two similar boxes could be close together, or a worker could have moved one between observations. When evidence is insufficient to justify merging, the coordinator should retain unresolved alternatives.

Time also needs to be distinguished. Capture time tells the receiver when the scene was observed; processing completion and message arrival describe later events in the pipeline. They remain useful for diagnosing delays, but using arrival time as the observation time can make an old scene appear current. Comparing capture times across robots requires clocks with a known relationship. If clock error is large relative to the event being analyzed, apparent timing differences may be misleading. The contract should make the time reference clear and define when an observation has become too old for a particular decision—an obstacle report may remain useful for scheduling after it has become unsuitable for deciding whether a narrow route is currently clear.

Uncertainty also needs more than a single score. The system may be confident that an object is a carton while having a poor estimate of its distance. A precise depth reading may accompany an uncertain object label. Glare may affect part of an image without invalidating every measurement from it. Combining all of these conditions into one confidence value leaves the receiving application unable to respond to their different consequences. For inventory, this distinction is especially tangible: a shelf label can establish which SKU belongs at a location, but it cannot reveal cartons hidden behind an obstruction. The count should cover what the robot actually observed; unobserved portions remain unknown, potentially requiring another observation or manual count to complete the task.

Provenance makes such questions possible to investigate. The report can identify the robot, sensor, and source observation, along with the processing version used to produce it. Where access and retention rules permit, a reference can lead to an image crop or recorded frame. That evidence need not travel with every message, but its availability and eventual expiry should be understood by the recipient.

As more sensors join, more measurements need reconciling. A camera may suggest the object’s type, while radar contributes range and radial velocity. Those readings can be combined only with appropriate spatial calibration, temporal alignment, and an assessment of whether they concern the same target. A radar return with no reliable camera match can remain an object of unknown type; inventing a label would conceal the disagreement. Fusion can take place at different stages, depending on what the downstream task needs and what each processor can handle. Cicalese cites Jason Huang’s account of Ambarella’s radar demonstration: a CV3 system-on-chip in the front radar unit processes data from five Oculii radar heads, then sends a combined point cloud to a zone controller for sensor fusion. A point cloud represents individual detections by their positions in three-dimensional space. That design keeps multi-radar processing together and gives the next stage a spatial representation. Other fusion tasks may need a different boundary, depending on which measurements the receiving stage requires.

Finally, Cicalese proposes that the interface contract should be tested by replaying reports from known scenes: starting with two observations of one box, then using two nearby boxes with similar appearances; introducing an old report after a newer one; removing the range estimate, changing the coordinate frame, and simulating a clock offset. Expected results should include how the coordinator handles uncertainty in each case. A useful test checks the downstream decision: if two reports cannot be associated confidently, the coordinator should preserve that ambiguity and follow the specified scheduling behavior, such as requesting another observation. A missing distance must not become zero, and a region hidden from the camera must not become clear space. Passing a message through a parser establishes much less than this.

When two robots report from opposite ends of Aisle 14, the server should have enough evidence to make a justified association—or enough information to recognize that another observation is needed. The coordinator’s assignment remains a proposal evaluated by the robot application runtime; motion remains subject to the machine’s separately validated protective control constraints. A well-designed report improves coordination without taking over those responsibilities.

Sources

  • ambarella.comAmbarella↗
Continue researching →