LLaVA-1.6: Improved reasoning, OCR, and world knowledge
llava-vl.github.io
llava-vl.github.io
Anyways, GPT4-vision wasn't always able to tell me that he doesn't really look the most comfortable being held, cause that's a lot of gravity pulling him down. Neither was Llava in the past. But with Llava 1.6 34B, it can, with no further questions asked besides "Please describe this image" as the first user message along with the image. So yeah this is really amazing! Its OCR has also definitely improved. Before, it'd just say text is in another language, but now it just shows the text. Can't wait to have a good enough computer to quickly run this locally.
I can't imagine how much of a difference it would make when vision models like this can be run at the edge in real time for blind users, including proper triage of relevant scene information narration.
Wild to think about the long tail of accessibility and how that's going to be wildly different with the improvements to generative AI.
>LLaVA-1.6 is trained with 32 GPUs for ~1 day, with 1.3M data samples in total. The compute / training data cost is 100-1000 times smaller than others.
Google's search appliances did the same thing before they were retired. Hospitals were especially keen on them. They eliminated HIPAA risks because data never left the hospital intranet, but then Google eliminated the product line in favor of cloud offerings.
> hyperlink based search ranking method of the day doesn't really work on relatively small data holdings of an individual organization
In my experience, it depends on what you mean by relatively small. Cloud editing and permissions aside, there seemed to be the 3 key factors:
1. Structure: hub-and-spoke sites interlinking crucial documents and pages
2. Culture: interdepartmental and personal rivalries which demand links as credit
3. Size: lots of employees creating and maintaining sites and content
I was too young to understand it then, but all of these help an intranet's content resemble the web of the 90s and 2000s. That's the era Google's algorithm was designed for.
The results weren't always perfect, but they were nearly always better than the alternatives. In-house or pre-existing alternatives tended to be awful, especially not having any search at all.
Keep in mind, all of this was ~10 years ago. My memory isn't perfect and a lot of things have changed since then.
I even made sure some of them did. It was my job at a few, but the relationships and boundaries between these were complicated. For convenience, let's say n_observed roughly equals 4.
I think you misunderstood: the organizations where PageRank worked best also put zero thought into it. I think it's more like holdovers from 90s and 2000s management trends emergently created an intranet structure which fit the assumptions underlying PageRank. Even interdepartmental tensions may have helped due to imitating the company behaviors of those eras.
[0] https://mildbyte.xyz/blog/llama-cpp-python-llava-gpu-embeddi...
My weekend hacking goal would be something like an RC car that can "drive to the largest plant in the room" or "go hide under the dining table" when prompted by voice. Slowly, by combining some sort of basic SLAM with still image promoting.
This looks quite promising: https://i.imgur.com/DnYWYPl.jpeg
Of course an alternative to doing it one-shot would be to collect lots of pictures + orientation for each, have LLaVA only caption them, then prompt a more generic LLM with that collected world info to pick where to go, etc.
What I like most about this AI stuff is how many neat things it makes achievable in a weekend by a motivated hobbyist that in the past required entire companies to tackle :). DIY/maker life in the AI age has been amazing fun do far.
Sending every frame to GTP-4 right now is way too slow. But at Tesla FSD like model can drive from one location to another in a closed environment with perfection. All that is missing is training that style in a roomba/robot form and then having GTP-4 monitor and manage the tasks at a 10 or 20 second interval
Reminds me of the recent HN post on jumping spider intelligence: They can do complex route planning, but need to stare for hours before they get going. This is probably more down to their tiny field of view on the front-facing good eyes, but still :-)
```ts
const CommentForm = () => { // State to hold the user's input const [comment, setComment] = useState(''); // State to hold the list of comments const [comments, setComments] = useState([]);
// Function for posting a new comment
const postComment = (e) => {
e.preventDefault();
// Add logic here to handle the POST request and update state
setComments([...comments, { content: comment }]); // Assuming you want the entire object in your state
setComment(''); // Reset the input field after posting
};
...
``````ts
import React from 'react'; import { CommentForm } from './CommentForm';
const App = () => { return ( <div> <h1>Comments</h1> <CommentForm /> {comments && <ul> {comments.map(comment => <li>{comment.content}</li>)} </ul>} </div> ); };
export default App; ```
Stage 1: Generate detailed description from image w/llava.
Stage2: Code the page using miqu 1.
My main interest with VLM is their ability to caption images, and this one seems very good honestly, this is going to be super useful to caption datasets.
I'm excited to see how this works in practice though.
* what scale are you running it at? Can this run in a production setting without blowing up budget (GPU == $$$)
* what usecases are you captioning for?
any other insights/lessons learned you could share?
I completely forgot how video encoders work, but I do remember that some encode the differences between one frame and the next with vectores of the "motion" of pixels. The training data would be comprised of frames from a video with labels assigned to time ranges across the length of the video.
The we could feed a video stream to a model and it would learn to not only recognise still images, but also motion across time.
Make it fast enough and we would have near real time inference of video.
If this works, maybe an extension to this model would be to accept its previous inference result as an input to the next frame inference request. Then we'd have results like "a person entered the bright light seen of a sunny day in the country side".
The article says the training costs are far lower, but it doesn't say how the inference costs compare (unless I'm missing it)
I’m specifically interested in processing smartphone photos of pages from an out of print book.
so far with my test gpt4-v seems to perform better, though very heavy on the censorship guardrails.
this 1.6 perfoms better than the previous version and seems to hallucinate a bit less.
Based on the demo linked in the article, you can specifically prompt "What is unusual about this image? Walk me through your reasoning step by step" and get a thorough understanding of the reasoning behind the LLM's response.
So, yes, words do have meaning, and the word "reasoning" appears apt.