LAION-AI / LAION-AI/CLIP_benchmark
Potential using mis-ordered KITTI prompt
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 814
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Thanks so much for providing such impactful works (LAION, Open CLIP, Open CLIP benchmark) to the community!
I noticed there might be a potential use of the mis-ordered KITTI prompt from https://github.com/openai/CLIP/blob/main/data/prompts.md#kitti
The prompt shared by Open AI is:
classes = [
'a photo i took of a car on my left or right side.',
'a photo i took with a car nearby.',
'a photo i took with a car in the distance.',
'a photo i took with no car.',
]
Here is the default order of the KITTI (distance) dataset:
above_20 below_20 below_8 no_vehicle
If we pair them:
above_20: 'a photo i took of a car on my left or right side.'
below_20: 'a photo i took with a car nearby.'
below_8: 'a photo i took with a car in the distance.'
no_vehicle: 'a photo i took with no car.'
Seems the right pair should be:
above_20: 'a photo i took with a car in the distance.'
below_20: 'a photo i took with a car nearby.'
below_8: 'a photo i took of a car on my left or right side.'
no_vehicle: 'a photo i took with no car.'
With the order chance, I can get 29.3 with the ViT-L/14 laion400m_e32 model.
Hope that could be helpful :)
Haoqi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the KITTI prompt definitions and the dataset's default class order in the benchmark code, then compare them with the mappings described in the issue and the referenced OpenAI KITTI prompt. Validate the corrected order with the KITTI evaluation using the ViT-L/14 laion400m_e32 model and confirm that the reported score is reproduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100