On this article, I talk about how one can advantageous(visible massive language fashions, usually referred to as vLLMs) like Qwen 2.5 VL 7B. I’ll introduce you to a dataset of handwritten digits, which the bottom model of Qwen 2.5 VL struggles with. We’ll then examine the dataset, annotate it, and use it to create a fine-tuned Qwen 2.5 VL, specialised in extracting hand-written textual content.
Overview
The principle objective of this text is to fine-tune a VLM on a dataset, an necessary machine-learning method in at the moment’s world, the place language fashions revolutionize the best way information scientists and ML engineers work and obtain. I will likely be discussing the next matters:
- Motivation and Aim: Why use VLMs for textual content extraction
- Benefits of VLMs
- The dataset
- Annotation and fine-tuning
- SFT technical particulars
- Outcomes and plots
Word: This text is written as a part of the work finished at Findable. We don’t revenue financially from this work. It’s finished to focus on the technical capabilities of contemporary vision-language fashions and digitize and share a worthwhile handwritten phenology dataset, which can have a major influence on local weather analysis. Moreover, the subject of this text was coated in a presentation in the course of the Data & Draft event by Netlight.
You possibly can view all of the code used for this text in our GitHub repository, and all data is available on HuggingFace. When you’re particularly within the extracted phenology information from Norway, together with geographical coordinates comparable to the information, the knowledge is instantly out there on this Excel sheet.
Motivation and Aim
The objective of this text is to point out you how one can fine-tune a VLM resembling Qwen for optimized efficiency on a selected activity. The duty we’re engaged on right here is extracting handwritten textual content from a sequence of photos. The work on this article is predicated on a Norwegian phenology dataset, which you’ll be able to learn extra about in the README in this GitHub repository. The principle level is that the knowledge contained in these photos is extremely worthwhile and might, for instance, be used to conduct local weather analysis. There’s additionally definitive scientific curiosity on this matter, for instance, this article on analysing long-term changes in when plants flower, or the Eastern Pennsylvania Phenology Project.
Word that the information extracted is offered in good religion, and I don’t make any claims as to what the information implies. The principle objective of this text is to point out you easy methods to extract this information and current you with the extracted information, for use for scientific analysis.
The outcome mannequin I make on this article can be utilized to extract the textual content from all photos. This information can then be transformed to tables, and you’ll plot the knowledge as you see within the picture under:

In case you are solely interested by viewing the information extracted on this examine, you may view it in this parquet file.
Why do we have to use VLMs
When trying on the photos, you might assume we should always apply conventional OCR to this downside. OCR is the science of extracting textual content from photos, and in earlier years, it has been dominated by engines like Tesseract, DocTR, and EasyOCR.
Nevertheless, these fashions are sometimes outperformed by the fashionable massive language fashions, notably those incorporating imaginative and prescient (usually known as VLMs or VLLMs)—the picture under highlights why you need to use a VLM as a substitute of conventional OCR engines. The primary column reveals instance photos from our dataset, and the 2 different columns evaluate EasyOCR vs the fine-tuned Qwen mannequin we’ll prepare on this article.

This highlights the principle cause to make use of a VLM over a standard OCR engine, to extract textual content from photos: VLMs usually outperform conventional OCR engines when extracting textual content from photos.
Benefits of VLMs
There are a number of benefits to utilizing VLMs when extracting textual content from photos. Within the final part, you noticed how the output high quality from the VLM exceeds the output high quality of a standard OCR engine. One other benefit is you could present directions to VLMs on the way you need it to behave, which conventional OCR engines can’t present.
The 2 important benefits of VLMs are thus:
- VLMs excel at OCR (notably handwriting)
- You possibly can present directions
VLMs are good at OCR as a result of it’s a part of the coaching course of for these fashions. That is, for instance, talked about in Qwen 2.5 VL Technical report section 2.2.1 Pre-Training Data, the place they listing an OCR dataset as a part of their pre-training information.
Handwriting
Extracting handwritten textual content has been notoriously troublesome up to now and continues to be a problem at the moment. The explanation for that is that handwriting is non-standardized.
With non-standardized, I check with the truth that the characters will look vastly completely different from individual to individual. For example of a standardized character, in case you write a personality on a pc, it’s going to constantly look very related throughout completely different computer systems and other people writing it. As an example, the pc character “a” seems very related regardless of which pc it’s written on. This makes it less complicated for an OCR engine to choose up the character, for the reason that characters it extracts from photos, most certainly, look fairly much like the characters it encountered in its coaching set.
Handwritten textual content, nevertheless, is the other. Handwriting varies broadly from individual to individual, which is why you typically wrestle with studying different individuals’s handwriting. OCR engines even have this precise downside. If characters fluctuate broadly, there’s a decrease probability that it has encountered a selected character variation in its coaching set, thus making extracting the right character from a picture harder.
You possibly can, for instance, have a look at the picture under. Think about solely trying on the ones within the picture (so masks over the 7). Trying on the picture now, the “1” seems fairly much like a “7”. You might be, after all, capable of separate the 2 characters as a result of you may see them in context, and assume critically that if a seven seems prefer it does (with a horizontal line), the primary two characters within the picture should be ones.
Conventional OCR engines, nevertheless, don’t have this means. They don’t have a look at all the picture, assume critically about one character’s look, and use that to find out different characters. They need to merely guess which character it’s when trying on the remoted digit.

The right way to separate the digit “1” from “7”, ties properly into the following part, about offering directions to the VLMs, when extracting textual content.
I might additionally like so as to add that some OCR engines, resembling TrOCR, are made to extract handwritten textual content. From expertise, nevertheless, such fashions aren’t comparable in efficiency to state-of-the-art VLMs resembling Qwen 2.5 VL.
Offering directions
One other important benefit of utilizing VLMs for extracting textual content is you could present directions to the mannequin. That is naturally inconceivable with conventional OCR engines since they extract all of the textual content within the picture. They’ll solely enter a picture and never separate textual content directions for extracting the textual content from the picture. Once we need to extract textual content utilizing Qwen 2.5 VL, we offer a system immediate, such because the one under.
SYSTEM_PROMPT = """
Under is an instruction that describes a activity, write a response that appropriately completes the request.
You might be an professional at studying handwritten desk entries. I offers you a snippet of a desk and you'll
learn the textual content within the snippet and return the textual content as a string.
The texts can include the next:
1) A quantity solely, the quantity can have from 1 to three digits.
2) A quantity surrounded by abnormal parenthesis.
3) A quantity surrounded by sqaure brackets.
5) The letter 'e', 's' or 'ok'
6) The p.c signal '%'
7) No textual content in any respect (clean picture).
Directions:
**Common Guidelines**:
- Return the textual content as a string.
- If the snippet accommodates no textual content, return: "unknown".
- So as to separate the digit 1 from the digit 7, know that the digit 7 all the time may have a horizontal stroke showing in the midst of the digit.
If there isn't a such horizontal stroke, the digit is a 1 even when it would appear to be a 7.
- Beware that the textual content will usually be surrounded by a black border, don't confuse this with the textual content. Particularly
it's straightforward to confuse the digit 1 with elements of the border. Borders must be ignored.
- Ignore something OUTSIDE the border.
- Don't use any code formatting, backticks, or markdown in your response. Simply output the uncooked textual content.
- Reply **ONLY** with the string. Don't present explanations or reasoning.
"""
The system immediate units the define for a way Qwen ought to extract the textual content, which provides Qwen a serious benefit over conventional OCR engines.
There are primarily two factors that give it a bonus:
- We will inform Qwen which characters to anticipate within the picture
- We will inform Qwen what characters appear to be (notably necessary for handwritten textual content.
You possibly can see level one addressed within the factors 1) -> 7), the place we inform it that it could solely see 1–3 digits, which digits and letters it could see, and so forth. This can be a important benefit, since Qwen is conscious that if it detects characters out of this vary, it’s most certainly misinterpreting the picture, or a selected problem. It might probably higher predict which character it thinks is within the picture.
The second level is especially related for the issue I discussed earlier of separating “1” from “7,” which look fairly related. Fortunately for us, the writer of this dataset was in step with how he wrote 1s and 7s. The 1s have been all the time written diagonally, and 7s all the time included the horizontal stroke, which clearly separates the “7” from a “1,” at the least from a human perspective of trying on the picture.
Nevertheless, offering such detailed prompts and specs to the mannequin is simply attainable as soon as you actually perceive the dataset you’re engaged on and its challenges. Because of this you all the time need to spend time manually inspecting the information when engaged on a machine-learning downside resembling this. Within the subsequent part, I’ll talk about the dataset we’re engaged on.
The dataset
I begin this part with a quote from Greg Brockman (President of OpenAI as of writing this text), highlighting an necessary level. In his tweet, he refers to the truth that information annotation and inspection aren’t prestigious work, however nonetheless, it’s some of the necessary duties you may be spending time on when engaged on a machine-learning undertaking.
At Findable, I began as an information annotator and proceeded to handle the labeling crew at Findable earlier than I now work as an information scientist. The work with annotation highlighted the significance of manually inspecting and understanding the information you’re engaged on, and taught me easy methods to do it successfully. Greg Brockman is referring to the truth that this work isn’t prestigious, which is commonly right, since information inspection and annotation may be monotonous. Nevertheless, it is best to all the time spend appreciable time inspecting your dataset when engaged on a machine-learning downside. This time will give you insights you could, for instance, use to supply the detailed system immediate I highlighted within the final part.
The dataset we’re engaged on consists of round 82000 photos, resembling those you see under. The cells fluctuate in width from 81 to 93 pixels and in peak from 48 to 57 pixels, which means we’re engaged on very small photos.

When beginning this undertaking, I first frolicked trying on the completely different photos to grasp the variations within the dataset. I, for instance, discover:
- The “1”s look much like the “7”s
- There’s some faint textual content in among the photos (for instance, the “8” within the backside left picture above, and the “6” within the backside proper picture
- From a human perspective, all the pictures are very readable, so we should always be capable to extract all of the textual content accurately
I then proceed by utilizing the bottom model of Qwen 2.5 VL 7B to foretell among the photos and see which areas the mannequin struggles with. I instantly seen that the mannequin (unsurprisingly) had issues separating “1”s from “7”s.
After this strategy of first manually inspecting the information, then predicting a bit with the mannequin to see the place it struggles, I notice down the next information challenges:
- “1” and “7” look related
- Dots within the background on some photos
- Cell borders may be misinterpreted as characters
- Parentheses and brackets can typically be confused
- The textual content is faint in some photos
We now have to unravel these challenges when fine-tuning the mannequin to extract the textual content from the pictures, which I talk about within the subsequent part.
Annotation and fine-tuning
After correctly inspecting your dataset, it’s time to work on annotation and fine-tuning. Annotation is the method of setting labels to every picture, and fine-tuning is utilizing these labels to enhance the standard of your mannequin.
The important objective when doing the annotation is to create a dataset effectively. This implies rapidly producing a number of labels and making certain the standard of the labels is excessive. To attain this objective of quickly making a high-quality dataset, I divided the method into three important steps:
- Predict
- Evaluation & right mannequin errors
- Retrain
You need to notice that this course of works properly when you’ve a mannequin already fairly good at performing the duty. On this downside, for instance, Qwen is already fairly good at extracting the textual content from the pictures, and solely makes errors in 5–10% of the instances. You probably have a totally new activity for the mannequin, this course of is not going to work as properly.

Step 1: Predict
Step one is to foretell (extract the textual content) from just a few hundred photos utilizing the bottom mannequin. The precise variety of photos you are expecting on does probably not matter, however it is best to attempt to strike a stability between gathering sufficient labels so a coaching run will enhance the mannequin sufficient (step 3) and taking into consideration the overhead required to coach a mannequin.
Step 2: Evaluation & right mannequin errors
After you’ve predicted on just a few hundred samples, it’s time to evaluation and proper the mannequin errors. You need to arrange your atmosphere to simply show the pictures and labels and repair the errors. Within the picture under, you may see my setup for reviewing and correcting errors. On the left facet, I’ve a Jupyter pocket book the place I can run the cell to show the next 5 samples and the corresponding line to which the label belongs. On the appropriate facet, all my labels are listed on the corresponding traces. To evaluation and proper errors, I run the Jupyter pocket book cell, make certain the labels on the appropriate match the pictures on the left, after which rerun the cell to get the next 5 photos. I repeat this course of till I’ve regarded by all of the samples.

Step 3: Retrain:
Now that you’ve just a few hundred right samples, it’s time to prepare the mannequin. In my case, I take Qwen 2.5 VL 7B and tune it to my present set of labels. I fine-tune utilizing the Unsloth bundle, which offers this pocket book on fine-tuning Qwen (the pocket book is for Qwen 2 VL, however all of the code is identical, besides altering the naming, as you see within the code under). You possibly can take a look at the following part to be taught extra particulars in regards to the fine-tuning course of.
The coaching creates a fine-tuned model of the mannequin, and I am going again to step 1 to foretell on just a few hundred new samples. I repeat this cycle of predicting, correcting, and coaching till I discover mannequin efficiency converges.
# that is the unique code within the pocket book
mannequin, tokenizer = FastVisionModel.from_pretrained(
"unsloth/Qwen2-VL-7B-Instruct",
load_in_4bit = False, # that is initially set to True, however you probably have the processing energy, I like to recommend setting it to False
use_gradient_checkpointing = "unsloth",
)
# to coach Qwen 2.5 VL (as a substitute of Qwen 2 VL), be sure you use this as a substitute:
mannequin, tokenizer = FastVisionModel.from_pretrained(
"unsloth/Qwen2.5-VL-7B-Instruct",
load_in_4bit = False,
use_gradient_checkpointing = "unsloth",
)
To find out how properly my mannequin is performing, I additionally create a take a look at set on which I take a look at every fine-tuned mannequin. I by no means prepare on this take a look at set to make sure unbiased outcomes. This take a look at set is how I can decide whether or not the mannequin’s efficiency is converging.
SFT technical particulars
SFT stands for supervised fine-tuning, which is the method of updating the mannequin’s weights to carry out higher on the dataset we offer. The issue we’re engaged on right here is sort of attention-grabbing, as the bottom Qwen 2.5 VL mannequin is already fairly good at OCR. This differs from many different duties we apply VLMs to at Findable, the place we usually train the VLM a totally new activity with which it basically has no prior expertise.
When fine-tuning a VLM resembling Qwen on a brand new activity, mannequin efficiency quickly will increase when you begin coaching it. Nevertheless, the duty we’re engaged on right here is sort of completely different, since we solely need to nudge Qwen to be a little bit bit higher at studying the handwriting for our specific photos. As I discussed, the mannequin’s efficiency is round 90–95 % correct (relying on the precise photos we take a look at on), on this dataset.
This requirement of solely nudging the mannequin makes the mannequin tremendous delicate to the tuning course of parameters. To make sure we nudge the mannequin correctly, we do the next
- Set a low studying price, to solely barely replace the weights
- Set a low LoRA rank to solely replace a small set of the mannequin weights
- Guarantee all labels are right (the mannequin is tremendous delicate to only a few annotation errors)
- Steadiness the dataset (there are a number of clean photos, we filter out a few of them)
- Tune all layers of the VLM
- Carry out a hyperparameter search
I’ll add some further notes on among the factors:
Label correctness
Label correctness is of utmost significance. Only a few labeling errors can have a detrimental impact on mannequin efficiency. For example, once I was engaged on fine-tuning my mannequin, I seen the mannequin began complicated parentheses “( )” with brackets “[ ]”. That is, after all, a major error, so I began trying into why this occurred. My first instinct was that this was as a result of points with a few of my labels (i.e, some photos that have been the truth is parentheses, had obtained a label with brackets). I began trying into my labels and seen this error in round 0.5% of them.
This helped me make an attention-grabbing commentary, nevertheless. I had a set of round 1000 labels. 99.5% of the labels have been right, whereas 0.5% (5 labels!) have been incorrect. Nevertheless, after fine-tuning my mannequin, it really carried out worse on the take a look at set. This highlights that only a few incorrect labels can damage your mannequin’s efficiency.

The explanation so few errors can have such a big influence is that the mannequin blindly trusts the labels you give it. The mannequin doesn’t have a look at the picture and assume Hmmm, why is that this a bracket when the picture has a parenthesis? (such as you would possibly do). The mannequin blindly trusts the labels and accepts it as a indisputable fact that this picture (which is a parenthesis) accommodates a bracket. This actually degrades mannequin efficiency, as you’re giving incorrect data, which it now makes use of to carry out future predictions.
Information balancing
One other element of the fine-tuning is that I stability out the dataset to restrict the variety of clean photos. Round 70% of the cells comprise clean photos, and I need to keep away from spending an excessive amount of fine-tuning on these photos (the mannequin already manages to disregard these cells rather well). Thus, I be sure that a most of 30% of the information we fine-tune accommodates clean photos.
Deciding on layers to tune
The picture under reveals the final structure of a VLM:

A consideration to make when fine-tuning VLMs is which layers you fine-tune. Ideally, you need to tune all of the layers (marked in inexperienced within the picture under), which I additionally did when engaged on this downside. Nevertheless, typically you’ll have compute constraints, which makes tuning all layers troublesome, and also you won’t must tune all layers. An instance of this might be you probably have a really image-dependent activity. At Findable, for instance, we classify drawings from architects, civil engineers, and so forth. That is naturally a really vision-dependent activity, and that is an instance of a case the place you may probably get away with solely tuning the imaginative and prescient layers of the mannequin (the ViT — Imaginative and prescient transformer, and the Imaginative and prescient-Language adapter, typically known as a projector).

Hyperparameter search
I additionally did a hyperparameter search to search out the optimum set of parameters to fine-tune the mannequin. It’s price noting, nevertheless, {that a} hyperparameter search is not going to all the time be attainable. Some coaching processes for big language fashions can take a number of days, and in such eventualities, performing an intensive hyperparameter search isn’t possible, so you’ll have to work together with your instinct to discover a good set of parameters.
Nevertheless, for this downside of extracting handwritten textual content, I had entry to an A100 80 GB GPU. The photographs are fairly small (lower than 100px in every route), and I’m working with the 7B mannequin. This made the coaching take 10–20 minutes, which makes an in a single day hyperparameter search possible.

Outcomes and plots
After repeating the cycle of coaching the mannequin, creating extra labels, retraining, and so forth, I’ve created a high-performing fine-tuned mannequin. Now it’s time to see the ultimate outcomes. I’ve made 4 take a look at units, every consisting of 278 samples. I run EasyOCR, the bottom Qwen 2.5 VL 7B model (Qwen base mannequin), and the fine-tuned mannequin on the information, and you’ll see the ends in the desk under:

Thus, the outcomes clearly present that the fine-tuning has labored as anticipated, vastly bettering mannequin efficiency.
To finish off, I might additionally wish to share some plots you can also make with the information.

If you wish to examine the information additional, it’s all contained in this parquet file on HuggingFace.
Conclusion
On this article, I’ve launched you to a Phenology dataset, consisting of small photos with handwritten textual content. The issue I’ve addressed on this article is easy methods to extract the handwritten textual content from these photos successfully. First, we inspected the dataset to grasp what it seems like, the variance within the information, and the challenges the imaginative and prescient language mannequin faces when extracting the textual content from the pictures. I then mentioned the three-step pipeline you need to use to create a labelled dataset and fine-tune a mannequin to enhance efficiency. Lastly, I highlighted some outcomes, exhibiting how fine-tuning Qwen works higher than the bottom Qwen mannequin, and I additionally confirmed some plots representing the information we extracted.
The work on this article is carried out by Eivind Kjosbakken and Lars Aurdal.