Skip to content

Conversation

…dFunction

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 7, 2022

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/90418

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit f1541f3:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

…evelAutogradFunction"

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
…evelAutogradFunction"

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
zou3519 added a commit that referenced this pull request Dec 7, 2022
…dFunction

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

ghstack-source-id: 5c9b4cf
Pull Request resolved: #90418
@zou3519 zou3519 requested review from samdow and soulitzer December 7, 2022 22:39
…evelAutogradFunction"

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
…evelAutogradFunction"

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
…evelAutogradFunction"

The API to do this is not pretty, but at least it works.

Test Plan:
- new test

[ghstack-poisoned]
Copy link
Contributor

@soulitzer soulitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

# a given name. A Tensor's .grad_fn field has a class name that is the original
# autograd.Function's name + Backward, so we do this to generate some
# meaningful name.
name = f'{autograd_function.__name__}Generated'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't feel super strongly about this, but just to bike-shed on the name a little, would SingleLayer be more informative than Generated to users at least since someone reading FuncGeneratedBackward might assume that Generated modifies Backward?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I hit merge before seeing this. Added it to the follow-ups issue.

I agree SingleLayer makes more sense.

@zou3519
Copy link
Contributor Author

zou3519 commented Dec 14, 2022

@pytorchbot merge -f "test failure is unrelated"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants