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
Empirical loss model for tidy3d mode solver #831
Conversation
Sourcery Code Quality Report❌ Merging this PR will decrease code quality in the affected files by 0.80%.
Here are some functions in these files that still need a tune-up:
Legend and ExplanationThe emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request. Please see our documentation here for details on how these metrics are calculated. We are actively working on this report - lots more documentation and extra metrics to come! Help us improve this quality report! |
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
=======================================
Coverage 74.66% 74.66%
=======================================
Files 425 425
Lines 20979 20979
Branches 2840 2840
=======================================
Hits 15664 15664
Misses 4444 4444
Partials 871 871 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
fixing pre-commit now |
Kudos, SonarCloud Quality Gate passed! |
Thank you Simon! |
Users can now empirically model the impact of surface scattering on waveguide propagation loss
This is done by adding a small parametrizable layer of imaginary index at the waveguide boundary as per this reference that can be calibrated to data. Top and side interfaces are treated independently.
While it is less robust than a full scattering treatment as per other references, the latter still requires external knowledge of RMS roughness and correlation length, in practice also calibrated from data. Both approaches also agree somewhat in the sense that ultimately, both only consider the overlap of the mode with the waveguide interface.
Example use:
This results in
Note that fine resolution is required, which makes this method better suited to FEM, see the new package femwell if interested