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

Why not add a new abstraction for different network topologies #65

Open
Alicegaz opened this issue Jul 8, 2022 · 0 comments
Open

Why not add a new abstraction for different network topologies #65

Alicegaz opened this issue Jul 8, 2022 · 0 comments

Comments

@Alicegaz
Copy link

Alicegaz commented Jul 8, 2022

Suggestions are to rename the models package to nn_components (or something more appropriate) and add a new package named topologies. Topologies will store classes for constructs of backbone, pooling, neck, and head, with different classes for each case which uses structure different from just stacking backbone, pooling, neck, and head or adds new components. This may be useful for models learned with AdversarialPropogation, Adversarial training or some cases of multiheaded learning, ensemble models or composite constructs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant