Faceplate reference regions drifting away from the physical marks

ImranBarnes0566 · 8 Jul 2026, 03:44 UTC

Reply to discussion
IM
ImranBarnes0566
I want accepted bright regions in our UR5e faceplate comparison as well as real defects. The present captions call moving streaks scratches, and I do not want the inspection scope reduced to whatever is easiest to see. What should establish the physical references and their correspondence with the camera images?

11 replies

IS
IsabelBell0648
Replying to ImranBarnes0566

Give each retained faceplate an identity and record quality's decision for the actual region under the agreed appearance method. Keep original captures and orientation references with it. A rejected plate may still contain an accepted bright band somewhere else.

6 points
IM
ImranBarnes0566
Replying to IsabelBell0648

Quality has judged the retained plates now: broad bands accepted, a short score near one mounting hole rejected. The full images are linked, but the exported annotation lies beside the hole rather than on the score identified by inspection.

5 points
AN
AnilBarnes0549
Replying to ImranBarnes0566

Do the annotation coordinates refer to the full capture or a resized or cropped view, Imran? Keep the existing files while checking that mapping instead of moving the arrow by eye until it looks plausible.

16 points
RE
RebeccaChan1126
Replying to ImranBarnes0566

And check the physical orientation reference. If the same-looking holes repeat, the right coordinates on the wrong orientation can still point somewhere convincing.

11 points
CA
CallumBrooks0795
Replying to RebeccaChan1126

Rebecca, yes, but don't make the inspector repeat the surface judgement just because an export disagrees. First establish whether the image and region mapping represent the same identified faceplate and orientation.

12 points
IM
ImranBarnes0566
Replying to ImranBarnes0566

Rebecca, orientation matches the asymmetric edge feature. Anil, the annotations were created on a crop but exported as full-frame coordinates without the crop offset. That explains this displaced region, not the physical quality decision.

21 points
IS
IsabelBell0648
Replying to ImranBarnes0566

Keep that correction separate from defect visibility. An accurately placed region can still contain a score the present camera view does not reveal under all allowed presentation conditions.

16 points
AN
AnilBarnes0549
Replying to ImranBarnes0566

Also verify more than this one region after correcting the export. Use known features at different image positions so the mapping check tests the coordinate transform, not one convenient arrow.

14 points
IM
ImranBarnes0566
Replying to AnilBarnes0549

The corrected export agrees at the checked full-frame positions, and the rejected score's region now matches the physical reference. Thank you, Anil; that was an actual mapping bug. Our controlled lighting comparison still loses the score at one allowed presentation.

21 points
CA
CallumBrooks0795
Replying to ImranBarnes0566

Then the reference mapping is repaired and the imaging candidate has a specific failure. Those are two useful results. Keep the failed presentation in the next comparison rather than letting the newly accurate annotation make the image look validated.

19 points
RE
RebeccaChan1126
Replying to ImranBarnes0566

Who owns the copied teaching exports? I'd withdraw the misplaced-region version now. The next lighting trial can remain unfinished without leaving people a known wrong reference picture.

20 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.