Lukas Chrostowski

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.

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...

Thank you for reporting this. It appears that Linux does not like the comma character. I have released an updated version that should fix this. On Tue, May 18, 2021...

This could be changed, but indeed the foundries usually only accept one dbu, so that should be defined in the technology.

create a text label, with “opt_in_TE_1550_xxxxx” on the Text layer, located at the tip of one of the grating couplers. You can also see the examples in the GitHub repository...

@jevillegasd I really like the automated SBends. In terms of performance, I added some lrcache functions late last year. Can you check if that improved the performance? For verification, indeed...

This is intentional. The waveguide paragrams are read from Waveguides.XML. These fields are read-only (though the GUI needs fixing).

Sure, do you have a suggestion? We can also skip the CML file, and leave it as “None” for a default.

On Windows 10 VM on my laptop, the above error doesn't occur. simulation completes. next error: fixed this error.