Hi,
I find Klayout product just now and tried Windows Klayout.
# My 2GB GDS make Klayout crash. This may caused by out of memroy(2GB) in Windows. I will try on Linux later.
Can you consider to read OpenAcess(OA) DB on Klayout?
# You may know that GDS can read into OA using strm2oa utility.
Regards,
-Kenji Morohashi-
Comments
Hi Kenji,
usually the memory requirements are somewhat lower than the (uncompressed) GDS file size (i.e. 1.4G load into 700M of memory). However, when the layout contains many properties attached to shapes or instances or a huge number of cells, the ratio may be larger.
If you start KLayout in viewer mode, memory requirements are somewhat lower. If you don't need the properties, you can disable properties in the "Reader options" dialog ("File" menu) by unchecking the "Enable properties" box.
OpenAcess to my knowledge is not under GPL which makes it difficult to incorporate into KLayout.
Best regards,
Matthias
Hi,
I seen that OpenAccess is available in LayoutEditor tool: https://layouteditor.org/layout/file-formats/openaccess
Maybe it can also be integrated into klayout ?
Regards,
Olivier
The OpenAccess license is not compatible with GPL.
You can lobby Si2 to give me a waiver. Until then, OpenAccess will not go into KLayout.
Matthias
I looked at an openaccess pdk and it sure seemed
full of proprietary data format stuff to me. Not sure
how "open" it really is. Other than branding.
Streamin to a Cadence database format or an "open"
format has nothing to do with opening the file native.
Other than Brand X's propensity to bloat.
Perhaps some "stuff" that is not pertinent to GDSII
found-layers display or editing could be filtered out
and compact the DB.
Who knows what kind of only-for-Brand-X crud is
in there occupying memory and demanding to be
parsed before it's stowed wherever junk goes?
How you'd do such a thing, no idea. But a set of
script GDSII input filters for known trash might be
popular as more folks try to use klayout for access
to commercial tool created layouts. It would be
unsurprising that CAD vendors find ways to tuck
extra, non-GDSII data up in the layout DB.