-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Suggest to add a second WAVEGUIDES.xml file for custom waveguide #150
Comments
Good idea, perhaps instead of importing WAVEGUIDES.xml we should just import every xml file containing "WAVEGUIDE". |
I have implemented this. I loads WAVEGUIDES.xml and then all WAVEGUIDE_*.xml files. It is on GitHub, but not released in Package Manager. Can you please check? |
Hi Mustafa,
Thanks for checking. I don’t see this problem on my end. Let me investigate further.
|
- sometimes Waveguides don't show up, and there is a "*" in the cell name. In this case it was when a string was a parameter when expecting a float.
I found an issue where a string representation of the bezier parameter caused the waveguide to not generate. Just fixed. Before updating, can you check if this problem only occurred for Bezier curve waveguides? i.e., you shouldn't have had this issue with non-bezier waveguides (e.g., TM). |
Hi,
Can we add a second WAVEGUIDES.xml file, e.g. WAVEGUIDES_custom.xml for custom waveguide configuration? Currently, custom waveguides and PDK waveguides share the same file. It needs to be remerged for every new PDK release.
Thanks,
Jin
The text was updated successfully, but these errors were encountered: