-
Notifications
You must be signed in to change notification settings - Fork 360
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
Documentation suggestions? #357
Comments
Other possibly very noob questions I ran into that I didn't find in the documentation include
|
Hi @cleong110 "b c h w" vs "b h w c" was important in DL 5 years ago, anyone knew that. Generation gap, I guess. Some comments can improve that.
ehm, no, I won't teach users to use meaningless axes
only ellipsis.
If you used asterisk, what would this mean? Don't ask 'what I can put in there'; ask 'can I do X'? Documentation covers a lot of cases, if you can understand 50% of them - that's already p95 of users.
Good catch, docstring needs to be updated |
Right, I suppose not... perhaps a better way might be to give two different meaningful labels, huh. Like:
This would get across to new users that they can assign the axes any name that is meaningful to them. |
I recently learned about einops, and decided to try and learn more. After reading all the way through I was still confused: "what do the letters mean? What is 'b'? What is 'h'?"
I iterally ended up Googling "einsum what do the letters mean", and found this thread, where someone explained that the letters can be anything. You don't have to use "b" or "h", you can use whichever labels you wish.
But if this is explained in the documentation, I could not find it. It just shows a number of examples, but I didn't see an example where the same thing is done but using different labels. An explanation or example up front would probably help, maybe something like this?
The text was updated successfully, but these errors were encountered: