Hacker News
Latest
Nvidia Starts Pac as AI Chip Maker Builds DC Influence Force
2026-08-27 @ 18:34:40Points: 89Comments: 40
Autism mutations drive neurodevelopmental pathology
2026-08-27 @ 18:23:43Points: 89Comments: 122
Previewing the Model Hardware Standard
2026-08-27 @ 18:04:50Points: 95Comments: 34
Show HN: Voronoi Go
2026-08-27 @ 18:03:37Points: 103Comments: 13
We found a division by zero bug in FFmpeg with a vibecoded fuzzer
2026-08-27 @ 17:53:40Points: 196Comments: 155
M5Stack Launches PaperMono
2026-08-27 @ 17:50:57Points: 102Comments: 42
Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
2026-08-27 @ 17:44:53Points: 32Comments: 13
Two German airport workers die of malaria after 'mosquito arrives on plane'
2026-08-27 @ 17:33:13Points: 169Comments: 93
Saving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache
2026-08-27 @ 17:17:57Points: 599Comments: 175
Gemini Omni 1.1 Flash
2026-08-27 @ 17:06:32Points: 204Comments: 148
Bild AI (YC W25) is hiring product and AI engineers
2026-08-27 @ 17:00:14Points: 1
Small Models Have Arrived
2026-08-27 @ 15:56:58Points: 528Comments: 238
Suica, Japan's First IC Transit Card
2026-08-27 @ 15:55:12Points: 211Comments: 183
Launch HN: Salem Robotics (YC S26) – Software for industrial inspection robots
2026-08-27 @ 15:46:04Points: 43Comments: 27
Here's a video of it running on real robot hardware with a few words from us: https://www.youtube.com/watch?v=U_228h3NE7c
We came to Salem through robotics research at UT Austin and a combined 15 years working in nuclear, including about 10 years developing and deploying autonomous robots at Los Alamos National Laboratory. Over the last five years, we kept running into the same gap: robot hardware had become very capable, but making a robot carry out a complete industrial procedure still required a surprising amount of robotics work and manual intervention.
The part that interested us most was manipulation. A nuclear contamination survey, for example, can require taking a "smear": wiping a defined area of a surface so it can be checked for removable radioactive contamination. In an oil, gas, or chemical facility, an LDAR (leak detection and repair) inspection can require moving a detector around a particular valve, flange, or connection. Other inspections require positioning an instrument at a precise location and orientation relative to a pipe or piece of equipment.
These are easy tasks to compress into verbs like "wipe", "measure", or "inspect", but considerably harder to make a robot do reliably. A probe might need to remain normal to a surface throughout a path, stay within a narrow offset from a pipe, or trace a region while maintaining a particular end-effector orientation. The planner has to find a feasible motion while respecting the task geometry, manipulator kinematics, joint limits, collisions, and the environment around it.
We work down to joint-level control for those interactions. One problem we've spent a lot of time on is generating constrained manipulation plans quickly enough that they can be based on the geometry the robot actually observes instead of requiring someone to carefully author a trajectory for every individual surface, valve, or flange.
The physical world makes this annoying. A few centimeters of error may not matter much when navigating down a hallway, but it matters if a sensor is supposed to remain normal to a curved surface. And successfully executing a trajectory doesn't necessarily mean the inspection worked. The detector could be misaligned, contact could be wrong, the geometry could differ from the model, or the measurement itself could be invalid. We care about closing that loop around the inspection result, not just whether the arm reached the commanded pose.
Our approach is a combination of AI and classical robotics. A lot of robotics research and industry attention right now is going toward increasingly end-to-end learned systems, particularly around humanoids. Working in safety-critical environments has made us appreciate how relevant classical approaches still are when you want explicit constraints, predictable behavior, and theoretical guarantees about what a robot can and cannot do.
We use AI where semantic understanding and flexibility are useful, such as interpreting less structured information or understanding what in an unfamiliar scene is relevant to a procedure. Once the system knows what physical interaction it needs to perform, we prefer explicit geometry, planning, optimization, and control where possible. We're interested in the marriage between the two rather than trying to make every part of the robotics stack learned.
The other idea behind Salem is that we don't think every useful robot application should require building a new robot. Companies like Boston Dynamics are getting very good at building increasingly capable hardware platforms. We think there is room for a domain-specific application layer on top of that hardware. The same underlying robot might perform nuclear radiological surveys in one facility and LDAR inspections in another, but the procedures, sensors, manipulation constraints, success conditions, and outputs are different.
That's also why we're hardware agnostic. We don't expect one robot to be the best platform forever, and facilities already own different hardware. We'd rather describe an inspection in terms of what needs to happen and then map that onto the capabilities of the right robot for the job.
One thing that surprised us after spending more time with facilities is how manual many inspection workflows still are. In sophisticated nuclear and industrial sites, people still physically walk survey routes, take measurements one at a time, visually inspect equipment, record results manually, and sometimes make judgments based on things like how a component sounds. Some of the basic workflows would be recognizable to someone doing the job decades ago, even though the sensors, computation, and robots available today are radically different.
We're starting with radiological inspection in nuclear because it's the industry we know best, and we're also working on manipulation-heavy inspection problems in oil, gas, and hazardous chemical facilities. The technicians and inspectors still define the procedure, interpret results, and make the consequential judgments. We're trying to automate more of the repetitive physical execution that currently requires someone to enter the environment or manually operate a robot.
We sell directly to industrial facilities, usually starting with a paid technical validation and then moving to an ongoing deployment. Pricing varies substantially with the workflow: validations range from tens of thousands to over $100k, and larger deployments can range from the low hundreds of thousands to roughly $500k per robot.
One thing we're especially curious to hear HN's thoughts on is where the abstraction boundary in robotics should sit. What should come from the robot manufacturer, what belongs in an application layer, and what will inevitably remain specific to the facility? We'd also be interested in hearing about other industries where you've seen physical inspection tasks that look trivial to a person but are surprisingly difficult to automate.
Engineered yeast for converting plastic and biomass compounds into food
2026-08-27 @ 15:40:04Points: 88Comments: 64
The terrifying mechanics of the Nepali flash flood
2026-08-27 @ 15:13:26Points: 92Comments: 51
Decompiling a Nintendo 64 game in 84 days
2026-08-27 @ 15:01:11Points: 199Comments: 124
Launching Route 53 Files
2026-08-27 @ 14:45:23Points: 107Comments: 38
Show HN: Restoredrill – proves your Postgres backups restore
2026-08-27 @ 14:16:23Points: 44Comments: 21
507 Mechanical Movements
2026-08-27 @ 14:08:18Points: 514Comments: 69
Trade (and Tariffs)
2026-08-27 @ 13:49:29Points: 487Comments: 239
Emacs 31: An unofficial guide to Markdown-ts-mode
2026-08-27 @ 13:22:36Points: 158Comments: 65
Aphantasia Beginner's Guide
2026-08-27 @ 13:14:20Points: 146Comments: 365
Microduck
2026-08-27 @ 10:57:56Points: 551Comments: 191
Show HN: The load-bearing vocabulary of Claude
2026-08-27 @ 08:59:49Points: 397Comments: 186
Humanity has the debate about AI consciousness backwards
2026-08-27 @ 02:37:07Points: 92Comments: 298
Related: Don’t mistake chatbot intelligence for consciousness - https://www.economist.com/by-invitation/2026/08/20/dont-mist..., https://archive.ph/IeSZg