Comment by kccqzy
15 days ago
That’s something Opus can also do. Perhaps by coincidence I also recently debugged shader bugs where Opus dumped the resulting render to PNGs and then using Python PIL to do comparisons. It purposefully added false colors too.
Suspect there is a training set going around focused on comparing and extracting data in distinct steps from image input. Saw it first on Opus 5 on a backpack construction task to extract and compensate for a reference tape being slightly offset in a LIDAR scan, followed by heat maps for per pixel comparison between the reference and blender render. Opus 5.5 did go a step further in the same, extrapolating offsets to compensate for capture inconsistencies. Some may not even notice this happening as Claude Code steers the model to use the scratchpad hiding much of this work.
Found this especially impressive because backpack material related research has been something I know models can still get caught up on and the models being decent at web research in coding nowadays does absolutely not apply to these task equally Recommending nylon canvas shell suppliers or waxed cotton when PVC coated cotton is explicitly request, that sort of thing. While not perfect in reading coding docs, models are far better there.
Like with front end and code “parsability”, feel like you can very clearly point at which labs use what training set, with many often sharing the same suppliers. Once I noticed that, I became very bullish on specific training sets over emergence as the source for current gains.