stefanottili
stefanottili
IOTIMINGS seem to be so ancient that this issue can be closed.
One strategy to avoid excessive memory consumption is to monitor the scanline memory requirements. If they exceed a certain threshold, stop operation and divide the chip/tile recursively into smaller pieces...
Given enough memory, klayout does the right thing, the problematic case is so unusual that just skipping xor'ing this particular layer is good enough, see https://github.com/KLayout/klayout/issues/1668 But in order for...
If this get's addressed, it would be very helpful if the "By Category" would be either always expanded or that the expand state of “by category” and “by cell” would...
I read rdb via command line, but that shouldn’t matter. So it seems to be a Mac issue too. With both homebrew 5.15.13 and 6.6.2_1 the tab splitter and the...
I build klayout with homebrew qt 6.7 on MacOS and the tab sizes are persistent now !!! Yay. So this bug report can be closed. It still would save me...
``` klayout Waveguide01.gds Warning: Record length larger than 0x8000 encountered: interpreting as unsigned (position=118, record number=9, cell=gdss) Warning: Record length larger than 0x8000 encountered: interpreting as unsigned (position=120086, record number=29,...
https://github.com/klayoutmatthias/dump_oas_gds2 should help to figure out what the “unexpected element” might be.
There was a similar question a couple of month ago. https://github.com/KLayout/klayout/issues/1424 Do a debug build, use valgrind’s callgrind and visualize the results with [kq]cachegrind. I found this to be a...
Just as another datapoint: On a MacBook M1 (4+4 cores) using 8 threads it takes 7m30s to build klayout from scratch. But I rarely do, a git pull followed by...