-
Notifications
You must be signed in to change notification settings - Fork 41
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
Added PECMedium to IsotropicUniformMediumType, and added PEC2D #1193
Conversation
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.
seems ok to me, do we need to add a changelog item in "fixed"?
Asking @shash-sharma for a review too since I'm not totally following the original problem this is fixing.
Sorry, what is the status of this? @shash-sharma ? |
I think we're waiting on PEC subpixel, and some revisions on this and the associated backend PR |
PEC subpixel will almost certainly not be in 2.5 - are you saying this and the backend PRs should then also not be labeled as 2.5? |
Weiliang had a proposal on the backend PR that could be implemented before
PEC subpixel as far as I am aware. I haven’t looked into implementing it
yet.
…On Fri, Oct 20, 2023 at 6:58 PM momchil-flex ***@***.***> wrote:
PEC subpixel will almost certainly not be in 2.5 - are you saying this and
the backend PRs should then also not be labeled as 2.5?
—
Reply to this email directly, view it on GitHub
<#1193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3KLECMVUT3NZAH73754YULYAK3U7AVCNFSM6AAAAAA5VWTZXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGE3DMMRVGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The issue is wanting a unified treatment of PEC across all three cases:
ordinary, anisotropic, and 2D.
On Fri, Oct 20, 2023 at 7:01 PM Charles Wojcik ***@***.***>
wrote:
… Weiliang had a proposal on the backend PR that could be implemented before
PEC subpixel as far as I am aware. I haven’t looked into implementing it
yet.
On Fri, Oct 20, 2023 at 6:58 PM momchil-flex ***@***.***>
wrote:
> PEC subpixel will almost certainly not be in 2.5 - are you saying this
> and the backend PRs should then also not be labeled as 2.5?
>
> —
> Reply to this email directly, view it on GitHub
> <#1193 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A3KLECMVUT3NZAH73754YULYAK3U7AVCNFSM6AAAAAA5VWTZXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGE3DMMRVGE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
daf7c5d
to
77bfb59
Compare
77bfb59
to
f21f491
Compare
@weiliangjin2021 do you want to change the meshing to use the relevant component even when another component is PEC? |
Could you edit |
One caveat in scene visualization is that only an isotropic PEC will be plotted as PEC. An anisotropic medium where some components are PEC is plotted as regular medium. Do you think it's fine @tylerflex ? |
It seems like |
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.
This makes sense to me. About the plotting, I think the current behaviour of only plotting isotropic PEC as PEC makes sense, since the anisotropic case with some PEC components seems to be a fairly special case, and probably used in a very different context.
@weiliangjin2021 , I pushed the changes we discussed. Also, I changed it to plot as PEC if any component is PEC, rather than if all components are PEC. Please check if this new handling makes sense. |
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.
One last comment. Otherwise all look good to me.
c469737
to
e0a5ee4
Compare
thanks for the catch. This should be ready, maybe we want to squash the commits though. |
Thanks, I'll take care of that. Usually we squash just before the merge so that changes can be better monitored. |
So is there anything left to do @weiliangjin2021 ? |
just start to squash and merge. |
e0a5ee4
to
5e34b8d
Compare
No description provided.