Branch and Bound for Relational Verification of Neural Networks
This paper introduces SaBRe, a branch-and-bound framework for relational neural network verification that improves efficiency and scalability by splitting relational neurons based on a dual-formulation selection strategy, outperforming existing baselines across multiple benchmarks.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are the safety inspector for a fleet of self-driving cars. These cars are powered by "neural networks," which are basically super-smart computer brains that learn to recognize things like stop signs or pedestrians by looking at millions of examples. But here's the catch: these brains can be a little too sensitive. If a stop sign has a tiny sticker on it, or if the lighting changes just a little bit, the car might suddenly think it's a speed limit sign and zoom right through. To keep everyone safe, we need to prove that the car's brain won't get confused by small changes. This is called "verification."
For a long time, safety inspectors only checked if the car could handle one specific change at a time, like "Will this car still see the stop sign if I add a tiny dot to the image?" But in the real world, we need to check something much bigger: "Will the car behave consistently no matter what the weather is like, or if the road is slightly wet?" This is called "relational verification." It's like asking, "If I drive the car in two slightly different scenarios, will it make the same safe decision in both?" The problem is that checking two scenarios at once is mathematically much harder than checking just one. It's like trying to balance two spinning plates at once instead of just one; the old tools often get confused and start screaming "Danger!" when there actually isn't any, or they miss real dangers entirely.
This paper introduces a new tool called SABRE (Splitting Approximated Bounds for RElational verification) to solve this tricky balancing act. Think of the old way of checking these cars as trying to fix a messy room by picking up one sock at a time. If the room is huge and the socks are everywhere, you might spend forever picking up socks and still miss the big pile of laundry in the corner. The authors realized that in the world of "relational" problems (checking two scenarios at once), the real mess isn't the individual socks (the single data points); it's the difference between the two piles of laundry.
So, SABRE changes the strategy. Instead of picking up one sock at a time, it grabs the difference between the two piles and splits that apart. Imagine you have two nearly identical maps of a city. The old method would check every single street on both maps separately. SABRE, however, looks at the tiny differences between the two maps and splits the problem based on those differences. If the maps disagree about a specific turn, SABRE zooms in on that disagreement immediately.
The researchers tested this new method on 817 different safety problems using standard datasets like ACAS Xu (for air traffic control), MNIST, CIFAR, and GTSRB (for image recognition). They found that SABRE was much better at solving these problems than the previous best methods. In fact, it solved significantly more problems and did so faster. For example, on the ACAS Xu dataset, SABRE solved 67 problems where the old method only solved 42. On the GTSRB dataset, it solved 33 problems compared to the old method's 9.
Crucially, the paper argues that the old way of splitting problems—focusing on individual parts of the network—is often the wrong move for these "two-at-a-time" checks. By focusing on the relationship between the two scenarios, SABRE cuts through the confusion much more efficiently. The authors also designed a smart "selector" that helps SABRE decide which difference to split next, kind of like a detective who knows exactly which clue to follow to solve a mystery the fastest. When they tested this smart selector against a random guesser, the smart selector solved way more problems, proving that knowing what to split is just as important as splitting it.
In short, the paper suggests that by changing how we break down the problem—focusing on the relationship between two scenarios rather than the scenarios themselves—we can make self-driving cars and other AI systems much safer and easier to verify. It doesn't solve every single problem in the world yet, but it shows a clear path forward that is significantly better than what we had before.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.