add Puffin-4M

[KangLiao929]

Datasets and benchmarks that span vision, language, and camera modalities remain scarce in the domain of multimodal spatial intelligence. To address this gap, we introduce Puffin-4M, a large-scale, high-quality dataset comprising 4 million vision-language-camera triplets. Puffin-4M includes single-view images with precise camera parameters, descriptive captions, pixel-wise camera maps, and spatial reasoning annotations across diverse indoor and outdoor scenarios. Beyond single views, it also incorporates cross-view and aesthetic images, making it a versatile benchmark for both understanding and generation tasks.

Summary by CodeRabbit

• Documentation
  • Added Puffin-4M benchmark entry to the research table, featuring Multimodal Spatial Intelligence and Reasoning with 4 Million Vision-Language-Camera Triplets, including arXiv paper link and GitHub repository reference.

[coderabbitai]

Walkthrough

A new entry for Puffin-4M dataset was added to the Visual-based data table in README.md, including links to its arXiv paper and GitHub repository, along with metadata indicating publication date 2025-10 and dataset size information.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added new row to Visual-based data table with Puffin-4M dataset entry, including arXiv paper link, image reference, publication date, and GitHub repository URL

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰✨ A puffin flies into our humble table row,
Four million visions in its wings aglow,
Spatial wisdom, camera triplets bright,
The README dances in October's light! 📚🎯

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'add Puffin-4M' directly and specifically refers to the main change in the pull request, which is adding a new entry for Puffin-4M to the README table.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9809ebc and 3c44d45.

⛔ Files ignored due to path filters (1)

• imgs/Puffin-4M.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[uncategorized] ~104-~104: The official name of this software platform is spelled with a capital “H”.
Context: ...Puffin-4M.png"> | 2025-10 | Github...

(GITHUB)

🔇 Additional comments (1)

README.md (1)

104-104: Entry looks good.

The Puffin-4M dataset entry is properly formatted, correctly placed in the Visual-based data table, and follows the established structure. The arXiv link, image reference, date, and GitHub repository link are all present and consistent with other entries in the section.

One small note: The static analysis tool flagged that the official platform name is "GitHub," but your project consistently uses "[Github]" throughout the file, which is fine as a project-specific convention.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}