# Loading the Mdeberta-v3-base

**URL:** <https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567>\
**Category:** Models\
**Created:** [March 13, 2025, 10:47am UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567 "2025-03-13T10:47:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mei234543](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@Mei234543](https://discuss.huggingface.co/u/Mei234543)\
**Post date:** [March 13, 2025, 10:47am UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/1 "2025-03-13T10:47:58Z")

</div>

While loading the “microsoft/deberta-v3-base” model, I am getting unexpected warning message.

Code : model = AutoModelForTokenClassification.from\_pretrained(“microsoft/deberta-v3-base”)

WARN : “Some weights of DebertaV2ForTokenClassification were not initialized from the model checkpoint at microsoft/deberta-v3-base and are newly initialized: [‘classifier.bias’, ‘classifier.weight’] You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.”

???: Why AM I seeing "DebertaV2ForTokenClassification " while loading V3 model.

Is the DEVs called the print warn function with different args?🧐🧐🧐

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [March 13, 2025, 5:18pm UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/2 "2025-03-13T17:18:22Z")

</div>

There are a number of possible causes, but the model hasn’t been updated for about two years, so if there is a problem, it’s probably because it hasn’t been updated since then, or because of changes to the library since then. Well, I think you can ignore the warnings and it will still work…😅

> <https://github.com/huggingface/transformers/issues/5421>
>
> \`\`\`
> model = AutoModelForSequenceClassification.from\_pretrained("bert-base-uncas…ed")
> \`\`\`
> 
> returns this warning message:
> \`\`\`
> Some weights of the model checkpoint at bert-base-uncased were not used when initializing BertForSequenceClassification: \['cls.predictions.bias', 'cls.predictions.transform.dense.weight', 'cls.predictions.transform.dense.bias', 'cls.predictions.decoder.weight', 'cls.seq\_relationship.weight', 'cls.seq\_relationship.bias', 'cls.predictions.transform.LayerNorm.weight', 'cls.predictions.transform.LayerNorm.bias'\]
> \- This IS expected if you are initializing BertForSequenceClassification from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPretraining model).
> \- This IS NOT expected if you are initializing BertForSequenceClassification from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
> Some weights of BertForSequenceClassification were not initialized from the model checkpoint at bert-base-uncased and are newly initialized: \['classifier.weight', 'classifier.bias'\]
> You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
> \`\`\`
> 
> This just started popping up with v.3 so I'm not sure what is the recommended action to take here. Please advise if you can. Basically, any of my code using the \`AutoModelFor\<X\>\` is throwing up this warning now.
> 
> Thanks.

---

<div class="post-metadata">

**Author:** ![Mei234543](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@Mei234543](https://discuss.huggingface.co/u/Mei234543)\
**Post date:** [March 13, 2025, 6:00pm UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/3 "2025-03-13T18:00:10Z")

</div>

I am not sure you can see the jpeg i have attached.

the model config itself is pointing to V2.

I wondering how those 158 finetunes are using, is it V2 or V3?

if V3, it’s totally fine but if V2 those guys are doomed for real after realizing.

 ![image](https://us1.discourse-cdn.com/hellohellohello/original/3X/7/7/77c3fa228b42a318e5a021129e4fe3d245545feb.png)

---

<div class="post-metadata">

**Author:** ![Mei234543](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@Mei234543](https://discuss.huggingface.co/u/Mei234543)\
**Post date:** [March 13, 2025, 6:00pm UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/4 "2025-03-13T18:00:44Z")

</div>

Is there a way to report this to devs?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [March 13, 2025, 6:05pm UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/5 "2025-03-13T18:05:38Z")

</div>

Generally, if the person you are talking to is an individual, sending a mention with @+username is a good way to get their attention, but if the person you are talking to is an organization, mentions don’t work.  
Also, since the person you are talking to is Microsoft and not Hugging Face, there is no way around it…

So, the most appropriate way to report this is to start a new discussion in the Discussion section.

> **[microsoft/deberta-v3-base · Discussions](https://huggingface.co/microsoft/deberta-v3-base/discussions)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [March 13, 2025, 6:08pm UTC](https://discuss.huggingface.co/t/loading-the-mdeberta-v3-base/145567/6 "2025-03-13T18:08:16Z")

</div>

However, there are cases where the code for the same model class can be reused, as is the case with Qwen 2 and 2.5. But V2 to V3 is probably a major version upgrade, so it’s probably still a bit strange.
