-
Notifications
You must be signed in to change notification settings - Fork 124
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
Updates to HDF5 metadata #192
base: master
Are you sure you want to change the base?
Conversation
…scales as well as tasks.
Looks good. Only issue I can think of is that this could be misleading if we save vectors or tensors in coeff space, since there the coefficients may correspond to spin/regularity components, not the coordinate components like in grid space. |
That's a good point. We could do something like s_1/2, s_-1/2, r_0, r_1, etc in that case, basis dependent? |
Yeah or maybe just |
Our ordering is {-, +, 0}. Using {-, +, 0} for both spin and regularity bases would be fine. But {s-, s+, s0} and {r-, r+, r0} might be a bit more descriptive. Don't think we ever have spin 1/2. |
Too much QM teaching...
…On Tue, Apr 26, 2022, 23:26 lecoanet ***@***.***> wrote:
Our ordering is {-, +, 0}. Using {-, +, 0} for both spin and regularity
bases would be fine. But {s-, s+, s0} and {r-, r+, r0} might be a bit more
descriptive. Don't think we ever have spin 1/2.
—
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7SHYNBTV3XPBPQXNH52RDVHCXXVANCNFSM5UMDX5TQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@jsoishi want to push this to a separate branch on the main repo? |
Marking as a draft since we're still WIP. |
coords
for tensor component dimensions populated from coordinate name strings from the CoordinateSystem object