Replies: 1 comment 3 replies
-
@Borda moved to discussions as this sort of issue isn't likely a bug on the timm end of things, you can try |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Not sure if the problem is my (user) side but running the same pipeline with the same dataset I getting very different F1 performance measures, see the following notebook with the only switch between TV and TIMM model
https://github.com/Borda/kaggle_iMet-collection/blob/main/notebooks/iMet-with-Lightning.ipynb
To Reproduce
Steps to reproduce the behavior:
timm.create_model('resnet50', pretrained=True, num_classes=dm.num_classes)
I get f1 about 24%net = LitResnet(arch='resnet50', num_classes=dm.num_classes)
I get f1 about 42% ; the model is implemented ashttps://github.com/Borda/kaggle_iMet-collection/blob/d1757e5bcc50065b0f92bddb6e3b40924f2c8819/kaggle_imet/models.py#L11-L22
Expected behavior
there performances shall be almost the same, not difference as double
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions