u/MadScientistsBase

Thought I'd make a little demo video showing the workflow behind the map scanner, and how I go from raw scan results to an actual candidate map.

Sorry for the scuffed video quality lol, I build tools not videos.

The demo shows, scanning without a reranker, switching to a trained reranker profile, inspecting candidates in 3D surface view, testing some custom scaling logic, and promoting a candidate into saved maps for later inspection

Last week I continued working on the custom scanner system and started expanding the profile personalization system alongside the mini-model reranker. You can now create your own custom profiles for different use cases and set stricter or softer limits depending on what you're trying to scan for.

You get full control over things like accepted map shapes, scanning stride (shorter stride for better BIN coverage but longer scan times), endian preferences, quality floor thresholds, max candidate counts, and more.

So alongside the mini reranker, you can also tune the profile’s “personality” toward the exact type of data or results you want it focusing on. Over time, the results should start becoming way more personalized to you and what that specific profile is built to look for.

I’ve been working more on the map comparison side for a little while now.

I didn’t really like was having to bounce between tables trying to mentally compare values.

So I wanted to build a view that lets me compare maps side by side, look at the raw values, and quickly switch between things like delta, absolute delta, and percentage difference so the changes are actually clear instead of trying to work everything out in my head.

From there, values can be edited manually or adjusted with quick tools like scaling, smoothing, and ramping.

Mostly I’ve just been focusing on removing friction from the process so the person using it can focus more on the actual calibration work instead of repetitive stuff that can be automated.

Would be curious to hear what other people would want in a map comparison workflow like this.

Started building this project a while ago with a few other developers.

Spent a lot more time on the visualization side recently and it's changed the way I go through unknown files quite a bit.

There's a huge difference for me between staring at the raw values in a table compared to being able to visualize the structure and behavior of the data properly.

Currently running, heatmap, 3D surface, contour, and histogram views.

Its been really useful for spotting gradients, sudden drop offs, noisy regions, and repeated patterns.

Been working on this with a few other developers for a little while now and honestly pretty happy with where it is getting.

A big focus has been building a custom trainable scanner for working with raw ECU bins.

The work flow is basically, load any bin, run a heuristic scan for candidate maps, and mark useful results / train against your own map files.

Over time the scanner starts prioritizing the kinds of maps you actually care about instead of needing to spend money buying predefined definitions.

I've been testing it across a mix of files lately (ME7, EDC16, SID807, etc) and it's been producing some very useful results.