Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Accurate in validation but got wrong result on new test data #153

Open
Barry-Liang opened this issue Jan 27, 2021 · 1 comment
Open

Accurate in validation but got wrong result on new test data #153

Barry-Liang opened this issue Jan 27, 2021 · 1 comment

Comments

@Barry-Liang
Copy link

Barry-Liang commented Jan 27, 2021

I have generated a custom dataset using the object data tools mentioned in this repository. After validation, the final result is as follow:
Screenshot from 2021-01-27 20-52-38

Screenshot from 2021-01-27 20-45-14
I think this result is very good. However, I want to use it in a real-time detection case. When I use the same camera and object to detect new data, the test results are totally wrong.
Screenshot from 2021-01-27 20-54-20

Screenshot from 2021-01-27 20-54-46

Screenshot from 2021-01-27 20-56-27

Screenshot from 2021-01-27 20-58-18

I am sure that the program I used to test the new data is correct. Because When I use it to test the original dataset, the results are all correct. But for the new data, the results are all wrong.

Do you have any idea about what happened?
I guess since the video is captured continuously, all the images in the test dataset have similar images in the train set, therefore the final result is still overfitted. But I am not sure.
I will appreciate it if you can help me with that.

@ValiaVl
Copy link

ValiaVl commented Sep 14, 2022

Hi @Barry-Liang . Can you share the code for visualizing the results on new unseen images without the ground truth labels required?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants