Closed cmp-nct closed 1 day ago
Has this been resolved?
I think we should temporarily remove "moondream" from the supported list, if someone else can confirm my findings ?
I can back up your findings. Using your example image and prompt I'm seeing the same behavior, the Transformers model gives the same answer as in your post, whereas the GGUF gives riveting answer like: Desk
, A brown table.
, A gray surface
, and so on.
And testing it on other images I also notice large discrepancies on some images, though it doesn't seem entirely consistent. There are some cases where both perform about the same, but yeah most of the time the GGUF is substantially worse.
Note that I used the same GGUF as you did, so it's possible the issue is in the GGUF itself.
@vikhyat can you please share the Python code you used for this? Thanks
@vikhyat can you please share the Python code you used for this? Thanks
Python code for inference? It's here: https://github.com/vikhyat/moondream
I tested moondream2 it does not work with the old llama.cpp version that supported VLMs.
This issue was closed because it has been inactive for 14 days since being marked as stale.
This issue was closed because it has been inactive for 14 days since being marked as stale.
What happened?
Moondream2 is a superb vision model, however on llama.cpp it performs at quality below vanilla llava-1 @vikhyat maybe you'd like to take a look ?
I compared images using python and using llama.cpp, both in fp16 format moondream2 does recognize images roughly, also the language part seems to work but the quality is totally off through llama.cpp When asked about spatial information (like lower left corner) it tends to just give anything from the left side or even a random object On python, the response is precise and surprisingly accurate.
I looked a bit deeper (https://github.com/vikhyat/moondream/blob/main/moondream/vision_encoder.py) and this appears to have support for multiple resolutions, while on llama.cpp it runs in llava-1.5 mode.
However, in my test image llama.cpp creates 729 input embeddings for the image, python did the same. So it's not just the input embedding count, something deeper is going wrong. My guess is that the sampling/patches are mixed up somehow.
For reference: moondream2 support was merged here: https://github.com/ggerganov/llama.cpp/pull/6899
Name and Version
abd894a
What operating system are you seeing the problem on?
No response
Relevant log output
Below is an example image:
Prompt:
<image>\n\nQuestion: What is in the lower left corner?\n\nAnswer:
Answer on python: "In the lower left corner, there is a green sticky note pad." Answer on llave-cli: "A cup of coffee is in the lower left corner." (I used the official supplied gguf files)