Ilan LewinPhysicist, engineer, three-time founder. Amstelveen.

Getting your measurement code off MATLAB and LabVIEW

If I sent you this, it's probably because something important in your company runs on a MATLAB script or a LabVIEW rig, and only one or two people can really change it.

I've been on both sides of that. I've written the lab code that proved a measurement worked, and I've been the one who had to turn it into a product other engineers could own. Thirty years of it: FPGA and RF at Netline, a multi-sensor platform at Kineti, robots now.

What usually hurts

• Licences that grow with every seat and every unit you ship.
• Hiring. Graduates know Python, not block diagrams.
• You can't diff or review a VI, so nobody dares touch it.
• The algorithm lives in MATLAB, the product in C, and the two drift apart.

How I'd get you out

1. Find the part that matters. Usually a small slice of the code carries the actual physics.
2. Record what the current system does on your real data. That becomes the test the new code has to pass, number for number.
3. Port it piece by piece to Python and C. AI does most of the reading and translating, the tests decide what's right.
4. Run old and new side by side until they agree. Your instruments mostly stay, they work fine with standard drivers.

How we'd start

Half a day with whoever knows the system, no charge. After that I can tell you what it would take, or that you're better off leaving it alone. If we go ahead, I work inside your team one or two days a week.