RuntimeError: running_mean should contain 1024 elements not 2048. about walkwithfastai.github.io HOT 15 CLOSED

Sorry, my bad, I didn't realize that wwf and timm are seperate libraries, updated wwf and now it's working.

from walkwithfastai.github.io.

Great! Glad to see it's working now

from walkwithfastai.github.io.

This should now be fixed!

from walkwithfastai.github.io.

I installed the latest timm version from pip: "0.3.4", but still receiving this error.

from walkwithfastai.github.io.

from walkwithfastai.github.io.

python3 -c "import fastai; import torch; import fastcore; import timm; print(torch.__version__, fastai.__version__, fastcore.__version__, timm.__version__)" 
1.7.0+cu110 2.2.2 1.3.16 0.3.4

from wwf.vision.timm import timm_learner

from fastai.vision.all import *


def label_func(f):
    return f[0].isupper()


path = untar_data(URLs.PETS)
files = get_image_files(path / "images")
dls = ImageDataLoaders.from_name_func(path, files, label_func, item_tfms=Resize(224))
learn = timm_learner(dls, "efficientnet_b2", metrics=error_rate)

learn.fit_one_cycle(3, slice(0.001, 0.03))

from walkwithfastai.github.io.

i am using an offline copy of timm (0.3.4) and wwf (0.0.10) in a kaggle notebook, and just got this error.
it actually ran perfectly earlier today, and was able to do a submission from that notebook.

fairly green to all this, but wanted to use an efficientnet in fast.ai so was so glad i discovered wwf!

RuntimeError: running_mean should contain 3072 elements not 1536

from walkwithfastai.github.io.

@davecampbell what is your version of fastai? Looks like it's not the most recent version

from walkwithfastai.github.io.

whatever is on the kaggle containers, i suppose.
!pip freeze produced:

fastai==2.1.8

from walkwithfastai.github.io.

You need to update fastai as well, as that is outdated. This fix is for versions > 2.2.4 I believe. This library will always be updated to the latest fastai version, which Kaggle will not always be

from walkwithfastai.github.io.

that sounds reasonable - let me work on getting that fixed and will report back. will also inform another fellow who said he had the same issue.
funky thing is that it actually ran error-free earlier today.
thanks so much for your attention.

from walkwithfastai.github.io.

i did load fastai 2.2.5 - but as it loaded, it said it was already there.
nonetheless, it ran after that - so i think that was the right advice!
thanks for that!

from walkwithfastai.github.io.

I ran a notebook last night, woke up this morning and re-ran it and it is giving me this error:
RuntimeError: running_mean should contain 4304 elements not 8608

Here is what happened with my frozen parameters.

from walkwithfastai.github.io.

from walkwithfastai.github.io.

fastai : 2.5.2
fastcore : 1.3.26
timm : 0.4.12

from walkwithfastai.github.io.