I see - so it doesn't help with converting to PCell (Polygons) which is what I want - thanks for clarifying.
Sorry having trouble remembering where I saw that warning - will let you know when I find it again.
I send OAS files from KLayout to our photomask vendor - they use both and have never had trouble with either.
@Max The 1st article linked also shows some thorough analysis showing that OAS produces significantly smaller files sizes than zipped-GDS,…
@Matthias I noticed that, when installing this vented font, KLayout had a notice saying "use a vector font" - have you seen, or have an example of a vector font that I can edit?
In my experience, I convert between OASIS & GDS all the time (for at least ~4 years), and the only annoyance that happens is when I save to GDS, the layer names get lost (which are retained in OASIS). Otherwise I have never noticed any differen…
@Matthias , How does the "BASIC.TEXT" PCell work? It appears to generate polygons based on input params - can't I use a similar approach to make a PCell that has input parameters of
1) cell to instantiate
2) x/y spacing
3) diameter to fil…
Thanks Matthias and @ravn ,
Ravn, I would indeed be interested in seeing how you accomplished that - passing PCell params to a script sounds perfect. I do want something more "dynamic", as one often needs to adjust the array (x/y-shift, …
Likely unrelated, but I see the following in syslog Console when I click "Run this script":
default 22:00:52.869980 -0700 klayout 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 716 vs 3318, 513,
Also, checking the properties option "show in Menu" doesn't appear to create a new item in the menu (after choosing a name for the item, and restarting KLayout).
In case anyone else, like me, was hoping to find instructions on how to use a "vented" font:
Vented font usage:
* Here is one example of a vented font - I just cut holes in the default "std_font.gds" from github:
* * vented_fon…
I also find myself repeatedly manually scouring masks for minimum gaps/widths. New users of our equipment don't know the resolution limits of our machines, so I have to manually drive around their designs looking for the minimum feature, hopefully…
@Matthias,
Are "Sessions" compatible between KLayout versions? (I suppose this could be the main difference between storing all info inside a GDS/OAS file.) I do intend to actually share the session files with other users when collabora…
SESSIONS - yes this is exactly what I wanted! Indeed the File>"save/restore session" function Stores/restores exactly what i'm seeing on my screen. Thanks!
Great, thanks for the link.
You're right that making that expression the default or a separate option (and fail safely/quietly) and adding an automatic "save *.LYP file" option, would make this whole process transparent (except for the fa…
So I guess the answer is "no", no single file format can reproduces the workspace, but there is a two-file workaround.
I have used lyp files. The process is cumbersome - if I want to share my layout work, I save the CAD file (as OASIS fo…
Thanks Matthias,
The report method is useful - i was outputting it to a layout. I'll give that a shot first. However even when i commented out the `output` command it would crash - by commenting out everything else, it seemed that it was the `odd…
I'm getting a hard-crash of KLayout when using the "odd_polygons" function.
The DRC appears to import ('input') the layers properly, and output them, but if I run "odd_polygons" on a layer with or without self-intersecting polygo…
Hello,
I am also trying to find self-intersecting polygons, and have been reading the DRC coding guidelines/definitions.
I am not seeing a "strange polygon" check, or other function like this. Could you point out where that function is,…
The best way I've found is to convert a raster image (eg. PNG, JPG) into vector (PDF) and then into DXF. I found InkScape was the best tool for this - although on MacOS you also have to install XQuartz (an X-windows system) to use it.
To convert y…