Asynchronous 3D understanding of photorealistic tiles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 7
- Avg merge
- 59m
- Merged PRs (30d)
- 16
Description
Look at the example and find a solution using this codebase
3D bounding boxes is a new experimental feature from Gemini 2.0 that will continue to improve in future models.
To get 3D bounding boxes, you need to tell the model exactly what you need for the output format. This is the recommended one as it's the one the model knows the best.
To prevent the model from repeating itself, it is recommended to use a temperature over 0, in this case 0.5. Limiting the number of items (10 in this case) is also a way to prevent the model from looping and to speed up the decoding of the bounding boxes. You can experiment with these parameters and find what works best for your use-case.
Contributor guide
No contributing guide indexed for this repository
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 with the linked Spatial_understanding_3d.ipynb example and inspect the repository's existing code related to maps and 3D tiles. The issue does not identify an entry point, test, or concrete acceptance criteria; clarify the intended depth-estimation and 3D-bounding-box behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100