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

Skip connection for ResNet type of GNN #164

Open
allaffa opened this issue Feb 21, 2023 · 2 comments
Open

Skip connection for ResNet type of GNN #164

allaffa opened this issue Feb 21, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@allaffa
Copy link
Collaborator

allaffa commented Feb 21, 2023

As the name suggests, the skip connections in deep architecture bypass some of the neural network layers and feed the output of one layer as the input to the following levels. It is a standard module and provides an alternative path for the gradient with backpropagation.

Skip Connections were originally created to tackle various difficulties in various architectures and were introduced even before residual networks. In the case of residual networks or ResNets, skip connections were used to solve the degradation problems (e.g., vanishing gradient), and in the case of dense networks or DenseNets, it ensured feature reusability.

@allaffa allaffa added the enhancement New feature or request label Feb 21, 2023
@allaffa allaffa self-assigned this Feb 21, 2023
@allaffa allaffa linked a pull request Feb 22, 2023 that will close this issue
@akhilpandey95
Copy link
Collaborator

hi, i have previously worked on building neural architecture search with skip connections. Can i contribute to this and help you build it ?

@allaffa
Copy link
Collaborator Author

allaffa commented Mar 14, 2024

@akhilpandey95
Thank you for reaching out to us.
Please send me an email to [email protected] and we will coordinate

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

Successfully merging a pull request may close this issue.

2 participants