When patterns are connected to each other, select and save are not complete, it will miss patterns.
I can only find a way not very straight to do this.
I can draw a pattern signaling which area I want to keep. Then, using boolean "and" function to get the overlaping area.
But when there are too many layers, it is cumbersome to write all those layers. Do there have some function giving all the layers in a layout?

For example, how to keep figures only in black box?

Best regards!
Weiling

I am looking for a way to rotate polygons by 45° on a dedicated layer but they should stay in place.
Practically saying I want to rotate tons of diamond shapes into orthogonal shapes, but the shape itself should remain in its position.

If I am using the rotate function while having multiple shapes selected, the origin of the shapes is also changed.

The array is shown in the screenshot while the regular rotation (having 2 shapes selected) is changing the origin and if I am rotating shape by shape the result is good... Any ideas Many thanks, Martin

I have seen that there's some kind of "use a second
GDS file as a library" capacity. I've found it a bit clunky
to copy between open layouts so have been just exporting
"done" devices to their own individual GDS file. Those
seem like my two options for corralling a herd of funky
one-off device layouts for a series of future products
(a lateral PNP is a lateral PNP, unless it's in a LM158).

But thought I'd kick off a discussion of how other people
(if anybody out there is going down the same or similar
road) like to approach this aspect of design management.

I’m trying to use RNetExtract to extract a net. My expectation was that the metal shape would be split into smaller pieces to form a resistor network, but the result only contains very few resistors. I also tried setting skip_simplify=True, but the outcome didn’t change much.

Is there a way to control or limit the size of each resistor segment when the metal is divided? With the current segmentation, the extracted resistors seem a bit inaccurate.

I’ve attached the script and the GDS file I used.

Thanks to you and your team,
dai

I'm currently using layout.read() to sequentially load multiple GDS files into a main layout and insert all cells into a top_cell. However, this process has proven to be quite time-consuming, and the bottleneck appears to be the sequential reading of each GDS file.

I've also thinking of use multiple layout to read concurrently, but the bottleneck becomes the copy_tree() part which copies all cells into the top cell.

I've also reviewed the reader source code in hopes of identifying potential optimizations for the read() function, but I haven't yet found a way to improve its performance.

May I kindly ask if anyone has experience with a more efficient approach to speed up this process? Additionally, do you believe there is still room to optimize the read() function itself?

Any insights or suggestions would be greatly appreciated. Thank you in advance!

I'm having difficulty checking the origin of an instance. The only method I'm aware of is double-clicking the cell's box when the levels are set appropriately, like so:

This works great when there's only 1 instance, however in this case where there's multiple overlapping instances, I have difficulty selecting the correct instance.

Are there other methods? A way to view the 'object properties' of multiple instances would be great

Thanks!

It seems K-Layout removes colinear points in polygons. I'm reading in external point arrays and creating the polygons like this:

p1=SimplePolygon.new(pts,true)
_cell.shapes(lyrnum).insert(p1)

This works fine, but some of the points are removed if the density is too high and the radius of the edges is too large.
Is there a way to remove/skip this processing? It messes up algorithms trying to extract the 'spine' of the polygon to calculate the path length and local radius of the waveguide patterns we make.

Thanks,

Dave

fatalword="(-2348.275000,-4985.623000),(-2348.275000,-4985.624000),(-2347.906000,-4986.132000),(-2347.505000,-4986.616000),(-2347.075000,-4987.075000),(-2346.616000,-4987.505000),(-2346.132000,-4987.906000),(-2345.624000,-4988.275000),(-2345.093000,-4988.612000),(-2344.542000,-4988.914000),(-2343.973000,-4989.182000),(-2343.389000,-4989.414000),(-2342.791000,-4989.608000),(-2342.182000,-4989.764000),(-2341.565000,-4989.882000),(-2340.942000,-4989.960000),(-2340.314000,-4990.000000),(-2339.686000,-4990.000000),(-2339.686000,-5180.000000),(-2340.314000,-5180.000000),(-2340.942000,-5180.040000),(-2341.565000,-5180.118000),(-2342.182000,-5180.236000),(-2342.791000,-5180.392000),(-2343.389000,-5180.586000),(-2343.973000,-5180.818000),(-2344.542000,-5181.086000),(-2345.093000,-5181.388000),(-2345.624000,-5181.725000),(-2346.132000,-5182.094000),(-2346.616000,-5182.495000),(-2347.075000,-5182.925000),(-2347.505000,-5183.384000),(-2347.906000,-5183.868000),(-2348.275000,-5184.376000),(-2348.275000,-5184.377000),(-2348.275000,-5126.411000),(-2347.961000,-5126.391000),(-2347.650000,-5126.352000),(-2347.341000,-5126.293000),(-2347.036000,-5126.215000),(-2346.738000,-5126.118000),(-2346.445000,-5126.002000),(-2346.161000,-5125.868000),(-2345.886000,-5125.717000),(-2345.620000,-5125.548000),(-2345.366000,-5125.364000),(-2345.124000,-5125.163000),(-2344.895000,-5124.948000),(-2344.680000,-5124.719000),(-2344.479000,-5124.477000),(-2344.295000,-5124.223000),(-2344.126000,-5123.958000),(-2343.975000,-5123.682000),(-2343.841000,-5123.398000),(-2343.725000,-5123.106000),(-2343.628000,-5122.807000),(-2343.550000,-5122.502000),(-2343.491000,-5122.194000),(-2343.452000,-5121.882000),(-2343.432000,-5121.568000),(-2343.432000,-5011.758000),(-2343.452000,-5011.444000),(-2343.491000,-5011.132000),(-2343.550000,-5010.824000),(-2343.628000,-5010.519000),(-2343.725000,-5010.220000),(-2343.841000,-5009.928000),(-2343.975000,-5009.644000),(-2344.126000,-5009.368000),(-2344.295000,-5009.103000),(-2344.479000,-5008.849000),(-2344.680000,-5008.607000),(-2344.895000,-5008.378000),(-2345.124000,-5008.162000),(-2345.366000,-5007.962000),(-2345.620000,-5007.777000),(-2345.886000,-5007.609000),(-2346.161000,-5007.458000),(-2346.445000,-5007.324000),(-2346.738000,-5007.208000),(-2347.036000,-5007.111000),(-2347.341000,-5007.033000),(-2347.650000,-5006.974000),(-2347.961000,-5006.934000),(-2348.275000,-5006.915000),(-2348.275000,-4985.623000)"
pattern_list= Array.new()


layoutView = RBA::Application::instance.main_window.current_view.active_cellview.layout
layout_view = RBA::Application::instance.main_window.current_view
current_work_cell= RBA::Application::instance.main_window.current_view.active_cellview.cell_name
layout = RBA::CellView.active.layout

fatalword.split("),(").each do  |xx|
pattern_list << xx.gsub("(","").gsub(")","")
end
puts pattern_list


layer1 = layout.layer(1, 0)
top = layout.cell(current_work_cell)
top.shapes(layer1).insert(RBA::Polygon::new(pattern_list))

is there a "lock cell" attribute, i can apply to this cell? or what is the way to prevent destroying done work?

Please see code below.
I would like to have 'r90' image with the exact same magnification 'r0' image.
What's the best way to do that?

Thanks,

def wait():
  counter = 1
  start = time.time()
  while True:
      time.sleep(0.1)
      if time.time() - start > 1:
          start = time.time()
          counter = counter - 1
          if counter <= 0:
              break

main_window = pya.Application.instance().main_window()
layout = main_window.create_layout(0).layout()
layout_view = main_window.current_view()

layout.dbu = 1

cell = layout.create_cell("TOP")

layer_index = layout.insert_layer(pya.LayerInfo.new(10, 0))

cell.shapes(layer_index).insert(pya.Box.new(0, 0, 1, 5))
cell.shapes(layer_index).insert(pya.Box.new(0, 4, 3, 5))
cell.shapes(layer_index).insert(pya.Box.new(0, 2, 2, 3))


layout_view.max_hier()
layout_view.select_cell(cell.cell_index(), 0)
layout_view.add_missing_layers()
layout_view.zoom_fit()

layout_view.set_config("global-trans", "r0")
wait()
box = layout_view.box() 
layout_view.save_image_with_options('c:/temp/r0.png',1000,1000,1,1,1,box,False)      

layout_view.set_config("global-trans", "r90")
wait()
box = layout_view.box()  
layout_view.save_image_with_options('c:/temp/r90.png',1000,1000,1,1,1,box,False)

But I find that there -is- no instance name to a placed cell. I find
no "handle", although the coords are shown attached to objects.
Perhaps the coords and name are the only handle. But seems
to me that a managed list ought to assign a name to each element
just to keep order (two objects could share same coords).

Being able to search by name is a great help, when it happens.
Forcing same name onto schematic and layout objects really
helps with LVS debug.

Am I just not looking in the right place or the right way? Or,
is this a thing which can be "brought to the surface" to let
us assign the names we want, and manipulate layouts using
them for our purposes?

is there a modifier for Ctrl+V to paste on the cursor position, do i have a wrong setting, or is this intended?

In the previous session I had removed the name (blanked) the field in
the Rename popup, like this:

but now something has been inserted (first pic) that is not what was in
the Layers Specification nor the Rename windows' fields.

Now on the flip side, the layer name I put by hand into the Edit>L.ayer>
Layer_Properties form has -disappeared- across an exit & restart. I had
made that field, the displayed name I wanted for each of the layers. Now
all gone. What is the point of a "write-only memory"? What purpose does
a data field that evaporates, have?

So there's two "name" fields neither of which will stay what I entered.
And behind it all is something that re-puts "a" name in the Layers window
that seems to be neither one. The displayed text in the Layers window is
neither field's content as of yesterday, case or characters-exactly. Close
but seemingly from some other source.

Questions -

• Which one "matters" to things like DRC / extract functioning and the
  compatibility od any code there?

• What data can be left out of the Layers window Rename fields without
  impairing functionality?

• Which of the fields (Layers window > Rename, Edit>Layer>Edit Layer
  Specification) should / needs to hold the One True Name? Or is there
  an even-more-meta, "real deal" field somewhere I'm not looking, to rule
  it all?

• Is there a "data flows from what, to what?" kind of exposition that tells
  "where I should be messing"? That is, specifically, "where does what I
  change, stick around and matter?"

• Am I even asking the right questions?

And somebody 'splain me again, what the "Layer Index" is, where it can
be seen and touched (permanently) through the GUI, and why or why not
someone might care and want to touch it? It seems to only appear in
documentation and as a "sorting" criterion but how to manipulate?

Also is there a way to toggle within klayout, a "freeze" to the layer basis
that "people who read the news" can't mess up, short of filesystem locks?
Like maybe just a settings-field up around where the technology defines
the .lyp autoload, which might make the loaded file only modifiable to
"visibility" and "validity" but not content behind that (no jacking names,
numbers, "order", for the end user of PDK unless they want to dig for
the radio button in Technology form somewhere)?

I think I've seen scattered hints about developing layers and technologies
"from scratch" but I could sure use the cookbook / "Dummies" version
if such a guide exists. That's different than the point-commands in
alphabetical order, as I'm finding out.

Thank you!

The code I use to merge different oasis files is given below.

layout_paths_to_import = ['layout.oas','layout2.oas']
top_cell_names_to_import = ['top1','top2']
output_layout_path = 'merged_layout.oas'
output_top_cell_name = 'output_top_cell'

def make_cell_instance(in_cell, angle=0, mirror=0, x=0, y=0, scale=1):
    trans=pya.CplxTrans(scale, angle, mirror, x, y)
    tmp_inst = pya.CellInstArray(in_cell.cell_index(), trans)
    return tmp_inst

def insert_cell_to_layout(layout,layout_path_to_import,top_cell_name_to_import,rotation=0,mirror=0,offset_x=0,offset_y=0,scale=1):
    top_cell = layout.top_cell()
    layout.read(layout_path_to_import)
    tmp_cell = layout.cell(top_cell_name_to_import)
    tmp_cellinst = make_cell_instance(tmp_cell, rotation, mirror, offset_x, offset_y, scale)
    top_cell.insert(tmp_cellinst)
    return layout

 output_layout = pya.Layout()
 output_layout.create_cell(output_top_cell_name)
 for layout_path_to_import, top_cell_name in zip(layout_paths_to_import, top_cell_names_to_import):
     output_layout = insert_cell_to_layout(output_layout, layout_path_to_import, top_cell_name)
 output_layout.write(output_layout_path)

Is there a more memory efficient way of doing this ?

I guess what I'd really like is a clean way to edit that .lyp without
wading through all the stuff I -don't- care about. So much of it is
neither name, layer, datatype or display. Now maybe somebody
else would care about different things.

There seems to be no "unified layer control and editing". Some
things are done in the layers panel, some under Edit>Layers,
a lot of jumping around. What about a panel that "has it all",
entry fields for texts and numbers, choosers for the display
attributes, one stop shopping that can load-from and save-to
the working layers (from there, the existing load / save for
filesystem)?

Of course I could use a clue meanwhile, about reassigning
layer indices independent of layer / purpose - I would like to
use the index to "lock down" the ordering of the layers, which
seems to be an option (but one that wants to use something
I don't know how to alter).

I'm using the XOR tool to compare 2 gds files but i don't want to compare the whole layout just 2 portions of the 2 layouts. I saw that there is the option Clipped to ruler but i could not see the layer differences on the klayout canvas. The Marker Database is showing the differences but when i click on them, i don't have the difeerences highlighted on canvas.

Do you have an idea on how to use the XOR Clipped to Ruler efficiently?

I want to convert this image file into GDS layout with same dimensions and the converted GDS file should be used for other layout operations like boolean operations etc.

I found one related discussion topic:
https://www.klayout.de/forum/discussion/comment/9119#Comment_9119

This image can be converted to GDS file using the details given in this link however the converted layout polygons has small small boxes of size = resolution and these boxes are not needed.

The converted GDS file should look like the layout file attached (remove .txt from input_layout.gds.txt) with only outer boundary layer (layer 1/0) and no boxes inside polygons.

One more requirement is to have this functionality in KLayout Python module (import klayout.db as db) so that I can integrate this piece of code with my other code written on KLayout Python modules.

Hello, I have a question about libraries. I've created some basic cells that I need to integrate into another one, but unfortunately, I can't seem to do that. I'm thinking that creating a library might be a good idea, but I don't know how to create a custom library. So, my question is: How do I create my own library? Do I need to write a script for this?

Thank you for your consideration and for taking the time to help me. I'm feeling quite frustrated.

Is this behavior something that the user
can modify?