> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/generative-ai/vision.md).

# Vision

Generative systems that see need a vision backbone whose features work for many tasks at once. This page points at one such foundation model, DINOv2, and then at one vision-generation case.

The same notes are in [Deep Neural Machine Vision](/deep-learning/deep-neural-machine-vision.md).

1. [DINOv2](https://dinov2.metademolab.com/): A Self-supervised Vision Transformer Model. A family of foundation models producing universal features suitable for image-level visual tasks (image classification, instance retrieval, video understanding) as well as pixel-level visual tasks (depth estimation, semantic segmentation).

Features are the understanding side; editing an image is the generation side. [Breast Augmentation Using Gen-AI](https://cohenori.medium.com/breast-augmentation-using-gen-ai-15492ab71f8b) (October 2024) is a vision-generation case, and the product frame is in AI Product. It is a guide to using AI to realistically alter human features in photographs, here a virtual breast augmentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.mlcompendium.com/generative-ai/vision.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.