We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently grid contains arrays for (k, l). Should we change to (kx, ky)? I'd vote "yes".
grid
k
l
kx
ky
grid.kx grid.kxr grid.ky grid.ksq grid.ksqr grid.invksq grid.invksqr
One would be tempted to use unicode, e.g.
grid.k² grid.k²r grid.k⁻² grid.k⁻²r
but that makes it rather cumbersome for new users...
Any thoughts?
@glwagner, @BrodiePearson, @liasiegelman
(The docs at the moment have a mixture of the two so it would be good to smooth it out after we settle on the issue.)
The text was updated successfully, but these errors were encountered:
@navidcy I agree that kx and ky is better than k and l. I prefer without unicode though.
Sorry, something went wrong.
No branches or pull requests
Currently
grid
contains arrays for (k
,l
). Should we change to (kx
,ky
)? I'd vote "yes".One would be tempted to use unicode, e.g.
but that makes it rather cumbersome for new users...
Any thoughts?
@glwagner, @BrodiePearson, @liasiegelman
(The docs at the moment have a mixture of the two so it would be good to smooth it out after we settle on the issue.)
The text was updated successfully, but these errors were encountered: