5 ms·
LLMs read images by splitting them up into e.g. 16x16 patches, which are then converted to embedding vectors and fed to the LLM, so from a technical point of vi
by johndough 26d ago
LLMs read images by splitting them up into e.g. 16x16 patches, which are then converted to embedding vectors and fed to the LLM, so from a technical point of view, feeding a big image as many 20x20 patches all at once is not too different from cropping subimages from the image, splitting those subimages into patches and feeding them to the LLM. Of course, the LLM has to be trained to understand that those images belong together, but it can be done.
- knollimar 26d agoYou say "it can be trained" but they fail at counting in my use cases, let alone maintaining symbolic relationships. Can you point me at one that can understand a detailed block diagram? Frontier is fine, soliciting recommendations
- johndough 26d agoFor counting, there are specialized counting models, e.g. https://huggingface.co/spaces/MengqiLei/count-anything-demo https://huggingface.co/spaces/MengqiLei/count-anything-demo I tried to parse hand-drawn ER diagrams in the past and did not have much success with any model, frontier or otherwise. If you have annotated data, I'd recommend finetuning a recent (dense) VLM, but don't expect 100% accuracy. https://unsloth.ai/docs/basics/vision-fine-tuning https://unsloth.ai/docs/basics/vision-fine-tuning
- knollimar 25d agogood advice; tbh I'm really trying to use counting as a proxy for "understand symbol, flag annotation next to it, associate annotation with symbol and store as object in location". Ideally, look at second diagram and see something similar in the same location and understand it's the same physical object.