-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
added adaptive_max_pool1d to frontend and ivy experimental #22982
Conversation
Thanks for contributing to Ivy! 😊👏 |
Hi @sherySSH |
@sherySSH Usually you shouldn't make frontend and ivy framework related changes in a single PR, those should be made as a separate PRs to keep things simple and clean. As @arshPratap mentioned, he had already made a PR on adding this function to ivy last week. Since his PR was created first, he would be continuing the work on adding the function to ivy. You could then make use of this function in the torch frontend you are working on. Again, sorry for the trouble and thanks for the contribution @sherySSH 🙂 . |
Ok noted. Since frontend was dependent on ivy implementation therefore I thought maybe both of these will go under 1 PR. Thanks for making it clear though, I will keep it under consideration next time. As soon as, @arshPratap adds function in ivy then I will use it in frontend to complete my sub-task. Cheers! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sherySSH
Sorry for delays on our end. I will take over the PR and get the other PR mentioned above merged and then get this merged hopefully. The first one implement adaptive 1d max pool in ivy and this PR uses it to impment it in the frontend.
So could you remove the logic from ivy experimental layers as this will just conflict with the updates from the other PR.
Let me know if anything is unclear. Thnx a lot :)
This PR has been labelled as stale because it has been inactive for more than 7 days. If you would like to continue working on this PR, then please add another comment or this PR will be closed in 7 days. |
This PR has been closed because it has been marked as stale for more than 7 days with no activity. |
PR Description
Related Issue
Close #22238
Checklist
Socials: