Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purpose allow_negative_crop in train_pipeline of MM Grounding DINO #11723

Open
AwePhD opened this issue May 16, 2024 · 0 comments
Open

Purpose allow_negative_crop in train_pipeline of MM Grounding DINO #11723

AwePhD opened this issue May 16, 2024 · 0 comments
Assignees

Comments

@AwePhD
Copy link
Contributor

AwePhD commented May 16, 2024

Hello,

In the base config of MM Grounding DINO, the train_pipeline has a RandomCrop with its allow_negative_crop set to True. Namely, the pipeline can produce an image with no bounding boxes on it.

My question is: why is it there? The BaseDataset.__getitem__ already use a refetch in case the transform return None. I do not see the point to use compute time on frame with no annotations.
Anyone can help me to understand this settings please?

Have a nice day,
Mathias

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

No branches or pull requests

2 participants