简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

The scratch labels look less certain than the images suggest

CarlaBarnes0575 · 2026年7月9日 12:52 UTC

回复讨论
CA
CarlaBarnes0575
Our planned presenting reflective components for surface inspection in a robot-presented camera station has Fairino FR5 presenting a reflective aluminium bezel to a fixed camera. The example images contain bright streaks that shift with small presentation differences, yet those streaks are being labelled as scratches. Before commissioning, I'd like to establish reliable references and image conditions for threshold tuning

18 条回复

FA
FarahAli0243

@CarlaBarnes0575 Check whether the suspected scratches were confirmed on physical samples under the agreed appearance procedure. Link each image to its sample identity and inspection result first.

12
CA
CarlaBarnes0575

Some labels came from the pictures alone. We still have the samples, but those labels aren't tied to physical inspection results. That's irritatingly circular

13
FA
FarahAli0243

@CarlaBarnes0575 Keep the image-only labels uncertain pending physical inspection. A controlled comparison of lighting and presentation can then investigate whether the moving streaks indicate reflection effects.

8
RE
ReeceChan1080

A scratch's visibility can change with presentation too. Don't let 'moving streak' quietly become the rule for relabelling something acceptable.

-6
FA
FarahAli0243

Correct. I meant a reason to investigate the imaging, not a new defect label. Physical acceptance stays with the agreed inspection method.

10
CA
CalebChen1189

So uncertain isn't the same as good? Where do those images go?

14
FA
FarahAli0243

Retain their sample identities and undecided status. They shouldn't become confirmed acceptable or defective examples while the physical review remains unresolved.

16
CA
CarlaBarnes0575

@FarahAli0243 Our two comparison folders changed exposure and presentation together. I can't tell which change made the images look better. That comparison needs a caveat too

25
NI
NinaBennett0762

On my inspection setup, a folder called 'better lighting' also contained easier samples. The folder name was doing a lot of unearned work.

16
CA
CarlaBarnes0575

What did you keep beside each image? I can manage sample ID and settings, but I don't want a form nobody fills in

25
NI
NinaBennett0762

On my setup we kept sample ID, exposure, lighting arrangement and presentation condition. Enough to explain a comparison without reconstructing the whole session from memory.

20
FA
FarahAli0243

Those records can support the vision specialist's comparison of image conditions. Holding the representative sample set constant will make an acquisition change easier to assess.

6
CA
CalebChen1189

Would a learned model just cope with the lighting differences?

12
FA
FarahAli0243

It still needs trustworthy labels and representative evaluation. A different model doesn't establish whether your reference scratches are real or your acquisition comparison is fair.

8
RE
ReeceChan1080

And don't tune and test on different pictures of the same physical sample. That isn't the independence the result would suggest.

15
CA
CarlaBarnes0575

I'll keep all images of one sample together when we split tuning and evaluation sets. Our file names alone wouldn't have caught that overlap

22
CA
CarlaBarnes0575

The reference problem is clearer, but I still can't judge inspection performance from our example images. The physical labels and image comparisons need more work

19
FA
FarahAli0243

The remaining physical-label and comparison work explains the open judgement. Clearer uncertainty doesn't yet establish inspection performance.

18

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。