Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add EfficientNet architecture #478

Closed
JacobGlennAyers opened this issue Apr 22, 2022 · 1 comment
Closed

add EfficientNet architecture #478

JacobGlennAyers opened this issue Apr 22, 2022 · 1 comment
Assignees
Labels
feature request New feature or request
Milestone

Comments

@JacobGlennAyers
Copy link

We noticed that the new BirdNET-Analyzer framework has migrated into using EfficientNet. I was curious if there have been any experiments with OpenSoundscape and Pytorch's EfficientNet capabilities?

@jatinkhilnani jatinkhilnani added the feature request New feature or request label Apr 24, 2022
@sammlapp
Copy link
Collaborator

Hi Jacob, thanks for your question. We haven't used EfficientNet so far with opensoundscape, but you could pretty easily use Pytorch's EfficientNet in opensoundscape if you wanted to by creating the EfficientNet object with an appropriate number of output nodes and using it as the "architecture" for the CNN class. (For examples of how we do this with other algorithms, see the cnn_architectures module.)

I'll leave this issue open. We'll probably add EfficientNet support (along with any other new architectures supported by PyTorch) in the next minor release.

@sammlapp sammlapp added this to the 0.8.0 milestone Sep 20, 2022
@sammlapp sammlapp self-assigned this Oct 4, 2022
@louisfh louisfh self-assigned this Nov 8, 2022
@sammlapp sammlapp changed the title Has EfficientNet been explored at all with this pipeline? add EfficientNet architecture Dec 20, 2022
@sammlapp sammlapp added the resolved_in_branch The issue has been resolved in a feat/issue branch but not merged into develop label Dec 21, 2022
@sammlapp sammlapp added resolved_in_develop The issue has been resolved in the develop branch but not in master and removed resolved_in_branch The issue has been resolved in a feat/issue branch but not merged into develop labels Jan 3, 2023
@sammlapp sammlapp removed the resolved_in_develop The issue has been resolved in the develop branch but not in master label Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants