-
Notifications
You must be signed in to change notification settings - Fork 50
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
Differentiable local field projection #1822
Conversation
9e2bc35
to
cecf530
Compare
👀 |
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.
a few comments. I'm mostly a little confused about the base.py stuff?
260293e
to
b387268
Compare
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.
Some comments.. Mostly things I thought could be refactored, renamed, simplified.
Otherwise I think it's consistent / correct. Only thing I'm not 100% sure on is in the DataArray.static
property.
vals = self.values if self.values.size == 0 else np.vectorize(getval)(self.values)
will getval
work if self.values
is a np.ndarray of dtype=object?
otherwise feeling pretty good about it in its current state
65ff9c3
to
5542fff
Compare
5ec140c
to
2fe0315
Compare
2fe0315
to
5bb4a0a
Compare
de9a4ba
to
3cd6ae9
Compare
52b3b7f
to
77c5973
Compare
c770e70
to
c5a5caa
Compare
@tylerflex There are some changes to |
c5a5caa
to
350d1db
Compare
@momchil-flex what do you think? basically there were some changes in my (recently merged) #1923 that Yannick used in this PR. So ideally we would do another develop -> pre/2.8 merge before Yannick rebases against 2.8? |
@yaugenst-flex what do you think will be simplest? I'm already running notebook tests for 2.7.3 and since it's hard to tell if this PR may not have various small effects, I'd rather not include it for now. However we could merge it to develop after 2.7.3 and then eventually into pre/2.8, or we can merge develop into pre/2.8 again and then you rebase the PR. Either way it will likely only come out in 2.8.0rc1 since we may not do any other 2.7. patches, but if we did the first approach would put it in there too. |
@momchil-flex I think it makes sense either way to merge develop into pre/2.8 after the 2.7.3 release so we keep them somewhat in sync. I'll rebase to pre/2.8 after that, shouldn't be a problem. |
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.
Looks really good! thanks @yaugenst-flex . I dont know if you want @QimingFlex to look at the field projection bits? I couldn't understand most of the physics of the operations, but did follow through the code and thought it looked good.
Hey @QimingFlex, would be great if you could have a quick look at the field projection bits in this PR, I reworked some of it to more easily accomodate autograd. I did try to make sure that all of the field projection values that come out of this are still exactly the same as before, but it wouldn't hurt to have another pair of eyes on it. |
c064c42
to
862d5b8
Compare
Hi @yaugenst-flex ,looks good to me, just a few questions regarding the surface current computation. |
862d5b8
to
963335b
Compare
9dbad53
to
6f6e8b8
Compare
….project_fields()`
c8cc84d
to
08ca4d6
Compare
No description provided.