If I were building a viewer for virtual staging comparisons, I would make the measurement state visible beside the score. The saved results for a loft kitchen, a white room with double doors and a cluttered open plan interior show why.
These are rooms 08, 09 and 10 in the VirtualStagingFlow results. Their score files contain image dimensions, alignment information, framing results and architecture measurements. Reading only the top level drift_score would discard information needed to interpret the number.
A missing measurement needs its own representation
The most revealing case is the white room. Its drift score is 5.7. Its alignment.ok value is false. Its framing.pass value is null, and the recorded result says "unknown (alignment failed)."
The alignment record reports 5 keypoints in the original and 197 in the staged image. Its reason is "too few keypoints." The architecture record says that the score falls back to the raw, unaligned comparison. It also records zero structural line pixels and null values for line recall, displaced line fraction and missing line fraction.
I would preserve those nulls when importing the JSON. Replacing them with zeros would assign a meaning that the file does not provide. A missing displaced line measurement cannot support the claim that no lines were displaced.
The same care applies to framing. Mapping a null framing value directly into a binary pass or fail badge would lose the recorded distinction. "Unknown" needs to survive the trip from the score file to the displayed result. This is an implementation recommendation drawn from the saved records, not a report of additional tests.
Compare successful alignment without expanding its meaning
The loft kitchen has a different measurement state. Its alignment succeeds with 173 inliers, framing passes, and its aligned architecture drift is 9.7.
The cluttered open plan room also aligns successfully. It records 87 inliers, a framing pass and aligned architecture drift of 24.5.
These records allow a developer to display aligned scores with an explicit framing outcome. They still do not justify generating a sentence such as "all walls preserved." The files contain comparison measurements, not an inventory certifying every wall, window and door.
All these architecture records specify an automatic mask covering the top 65% of the frame. That scope should remain attached to any explanation of what was evaluated. The open scoring methodology is the appropriate companion link for explaining how to read this kind of result.
Keep observations distinct from computed fields
I opened the comparison images before describing their contents. In the loft kitchen, the large exposed duct, ornate ceiling and tall patterned window remain recognizable. In the white room, the double doors and surrounding mouldings appear retained, and an office arrangement is visible beyond the opening, which does not resolve the failed automatic alignment. In the open plan room, the kitchen, intercom, closed door and upright elements remain recognizable after clutter removal and the addition of seating.
I would store such notes separately from computed fields in a comparison viewer, so a reader can distinguish a reviewer's inspection from a value produced by the scoring process.
Carry the run context forward
The test log records Contemporary styling, "Clear first," no custom request and the first output counting. It also discloses complimentary credits. Those details belong with the result because they describe the conditions under which the image was produced. In particular, the clearing setting explains why existing belongings disappear from the open plan photograph.
For a small viewer built around the StagingBench records, I would expose the source filename, alignment state, framing result, drift value, alignment status of that value and mask description, with the comparison image beside them.
Publication disclosure needs separate handling. The log records a disclosure file accompanying downloads without a burned in label. MLS rules vary, and a label on the image is commonly required. Neither a successful alignment nor a framing pass establishes compliance.
Top comments (0)