Matthias
About
- Username
- Matthias
- Joined
- Visits
- 16
- Last Active
- Roles
- Member
Comments
-
Hi David, You're right - exactly that's what it was meant for. I'll check why it isn't working. And the workaround is exactly what I had proposed too. Thanks for mentioning this. Matthias
-
Hi Lukas, I'm not saying it's not possible to use PCells inside PCells - if you want to place PCells inside others you can do so. I just feel it's more complicated this way. Regarding your workaround: It's a nice idea in fact. The background of t…
-
Hi David, you can subscribe to the RSS feed at the main page. It was intended to mirror the newsfeed. I hope it's working. Best regards, Matthias
-
Hi Shiriam, Maybe you can provide a screenshot (dropbox link or whatever platform you like)? A precise description of operations you perform is also helpful. Thanks, Matthias
-
Hi David, thanks for these nice pictures! This well prepared report would deserve an equally well-prepared response. But I think the solution is pretty trivial: it's a drawing bug I think. That happens always when "smooth" paths are pres…
-
Hi David, many thanks for this nice example! Best regards, Matthias
-
Hi Wing, can you paste the complete code, please? Thanks, Matthias
-
Hi Lukas, Ok, I see I'm not convincing ... :-) Here is another forum discussion with some pointers about the topic of calling PCells inside other PCells: http://klayout.de/forum/comments.php?DiscussionID=701&page=1#Item_4. Regarding your ques…
-
Hi Masaki, I had some short nights over this topic. But I think you're right and I have achieved some consolidated state now. The current implementation (going into 0.24.4) will feature * File level PROPERTY records are put before every other rec…
-
Hi Frings, I don't think you'll need scripting. Just try klayout -s 1.gds 2.gds 3.gds ... then edit the layer list using the functions from the layer list's context menu (delete, rename ..) and save the resulting layer properties to a .lyp file …
-
I wonder whether this helps against bugs too. Any experiences? Matthias
-
Hi Masaki, thanks for your analysis. Formally you're right. Although I think the BNF does not forbid using PROPERTY records after PROPNAME. But if I take 31.1 seriously then PROPERTY after PROPNAME means that the PROPERTY is associated with PROPN…
-
Hi Jack, maybe I should make the number of points a variable. To be frank I thought that 64 points for a circle are pretty smooth already. That snapping I can't explain. Maybe your input layout uses a 10nm database unit? The input's layout databas…
-
Hi Jonas, Yes, I know, that's a problem. Maybe one can re-issue the paint events lost. To me, the missing help feature is more annoying while I debug. Matthias
-
Hi Michael, thanks :-) In general, the code above is awfully old. Now there is the DRC feature which is much more convenient to use. Please see http://www.klayout.de/doc/manual/drc.html for details. But the DRC feature is also producing flat data…
-
Hi Masaki, I'm starting to get suspicious .. what exactly are you doing? So far nobody looked that deeply into the OASIS writer implementation :-) Well, never mind .. it's good you do this kind of review! I appreciate that! I shall help you by po…
-
Hi phil, I'm afraid I don't really understand your request. With a clear field mask you get glass where you have drawn something. If you have a darkfield mask you need to reverse the data. Is you request about inverting the layout for this case? …
-
Hi Frings, what do you want to do exactly? Open it for viewing or manipulation? There is a introduction into the scripting feature here: http://www.klayout.de/doc/programming/index.html. It's mainly for Ruby but there is a section about how to tra…
-
Hi Jack, To change the dimensions of your arena use "depth", "below" and "height": http://sourceforge.net/p/xsectionklayout/wiki/DocReference/#wzxhzdk12belowwzxhzdk13-wzxhzdk14depthwzxhzdk15-and-wzxhzdk16heightwzxhzdk1…
-
Hi, How should I know? How about giving some details? OS? Version? A code sample??? Matthias
-
Hi Lukas, it does not apply to produce_impl. With the above patches the sample and handles work for me on Linux. But given the observations regarding random crashes (see http://klayout.de/forum/comments.php?DiscussionID=758&page=1#Item_2) I th…
-
Hi Lukas, thanks for the stack traces and the helpful video. This stack trace looks pretty similar to what you reported some time ago (http://klayout.de/forum/comments.php?DiscussionID=734&page=1#Item_8). So I assume there is a general issue. …
-
Hi Lukas, yes, you're right. The Python's sample is not working as expected with respect to the shape to PCell translation. There is more than a single issue here. A workaround is to employ the "raw" methods, not the convenience methods …
-
Hi Masaki, you're right ... that happens on Windows 64 bit only. On Linux, 32 and 64bit behave correctly. I assume it's something with the way the VC++ handles the different data types. I'll try to fix that for 0.24.4. Thanks and best regards, M…
-
Hi Canny, this is a known bug. Please use the most recent version 0.24.3, where this bug was fixed. Regards, Matthias
-
Hi David, this is not intentional, but hard to avoid. Basically, leaving the main window alive during debugging sessions is a major cause of inconvenient crashes. Imagine you write code that plugs into the internals (i.e. handling mouse events or …
-
Hi Jonas, yes, you're right. The RecursiveShapeIterator is not a Python iterator - it's called an iterator because it implements the pattern, but it is no related to Python iterators in any way. next is simply a method of this class, so you cannot …
-
Hi Lukas, I think the proper way to write the above code is ...new_selection[new_selectionN].append_path(pya.InstElement(new_cell))... I guess the previous code was changing the "append_path" attribute to an InstElement which basically …
-
Hi Masaki, I am sorry, but can't confirm that. Here is a sample for a table written by KLayout: 000000013 01 START000000014 03 31 2e 30 version ("1.0")000000018 00 e8 07 resolutio…
-
Great. But this was not my achievement. There is an active community taking care of MacOS! Thanks to all of you, by the way. Specifically to Kazzz! Matthias