Matthias
Hi Jim,
you can use master or any other branch, but without warranty.
The usual approach (and the one favoured by GitHub) is: features are developed in branches. When they are considered stable enough they are integrated into the master (pull request). Hence the master is kind of "latest greatest", but with a certain risk of being spoiled. There are also forks from other user with their own masters and branches. Don't confuse them with the ones from the KLayout project.
But eventually, when the master is considered to have a sufficient quality, a release is made by creating a release tag (https://github.com/KLayout/klayout/releases). A release is a snapshot which is then turned into Windows binaries, Linux packages, PyPI wheels etc. This this is a lengthy process and I don't want to do this too often.
Matthias
About
- Username
- Matthias
- Joined
- Visits
- 1,513
- Last Active
- Roles
- Member
Comments
-
... and found and fixed the issue. That was a side effect of the memory optimization for DRC I did not have on my plate. I'll dispatch a 0.28.2 now. Will be released tomorrow. Quickest hotfix so far :) Matthias
-
After some trying I can reproduce the problem :( Sadly I just release 0.28.1. But maybe that is going to be a very quick 0.28.2 ... Matthias
-
"Schematic" should show the schematic netlist you loaded into LVS. Here is an example: (Image) So if your "schematic" is empty, this means no schematic has been loaded. Could you check - maybe there is something wrong there? M…
-
Oh well ... 0.28 got a new concept here as it supports multiple technology stacks per technology now. In the course of that development, I renamed this class to "NetTracerConnectivity" as that is what it describes (rather than a technolog…
-
Very good, thanks @"Vincent Lin" for helping. I think your code lacks a line which fetches "idxs". Actually, layer_indexes and layer_infos correspond. The "layer index" is not a sequential number as there are hidden …
-
Hello @NMF, first sorry for this delayed reply. Actually, libraries are a special concept that KLayout introduces. It is not a standard concept of GDS. This is why other tools do not known about that. GDS internally does not have connections to a…
-
You have to first create "variants". Use "Edit/Selection/Make Cell Variants". This will break the array and create a new cell specific for the location where your selected shape is in. After that you can edit this cell without af…
-
Sorry for the confusion, I had to try myself before understanding the problem. I have fixed that issue in 0.28 which has been released yesterday. Matthias
-
Fixed in master.
-
Sorry, stupid me. You're perfectly right. I can easily reproduce the problem Here is the ticket: https://github.com/KLayout/klayout/issues/1216 I'll fix it asap. Matthias
-
Thanks for this hint. I'll try to reproduce the issue myself. Matthias
-
@srjmas Thanks for your thoughts. I am aware that this feature is useful, but I am lacking the bandwidth to take care of this. I assume it is possible to integrate these tools with the help of some scripts. I'd appreciate contributions in that area…
-
@soumeniit Could you explain in more detail what you are doing and what is your expected outcome? Thanks, Matthias
-
Thanks. I still prefer the forum, but github tickets are easier to track and they connect to code changes + releases, so in terms of implementation they are more useful. Matthias
-
That's bad. Can you say where "original" comes from? Maybe there are more cases like the "extended" problem - although I don't know of one. Thanks, Matthias
-
@srjmas Thank you for your feedback. I cannot entirely rule out a bug in KLayout which generates duplicate cell names. Guaranteeing unique names unfortunately isn't easy unless you impose severe restrictions on the API. I am about to release the n…
-
I have created a ticket for a repair feature for future releases: https://github.com/KLayout/klayout/issues/1200
-
Sorry for the inconvenience - basically providing a pre-built dump_oas2 binary should not be an issue, but I'm kind of tired of CI configuration tasks. I'm not a DevOps engineer. I debugged your issue and actually it is a side effect of a duplicate…
-
Hi @laurent_c I assume that is deep mode, right? I think that "original" for some reason has a wrong binding. If "original" comes from "extended", the problem may be related to this bug: https://github.com/KLayout/kla…
-
Funny ... never noticed that myself. I created a ticket for this: https://github.com/KLayout/klayout/issues/1199 Thanks for mentioning this. Matthias
-
File a ticket on github please: https://github.com/KLayout/klayout/issues
-
I see ... thanks for the link! I'll stay optimistic :)
-
@Grandement Thank you for sharing this! Matthias
-
Ah, right. These layer numbers are internal ones and there is no representation for that in the original layout. Matthias
-
My proposal was size and move by half the size amount. At least that is how I would implement it internally :) So like: # bottom and left sized by 1µm:sized_bottom_left = original.sized(0.5.um).moved(0.5.um, -0.5.um) This simple solution suffers …
-
Let's see - I am in touch with some people about this. It's all about how open SEMI is and how willing they are to collaborate with Open Source. DXF IMHO does not qualify for mask data transfer as it does not even have a concept of "inside&quo…
-
@Ege_Bey The stream readers/writers are dynamically loaded. You have to supply them separately I assume. If pyInstaller does what I think it does, it will analyze the DLLs and package all dependencies. I cannot know about dynamically loaded librarie…
-
Okay, the application should not crash ... but you're passing an invalid layer id to get_info. get_info takes a layer ID which you get when you know the GDS layer number/datatype. A layer ID is an internal layer index and typically is a low number.…
-
Very good. If the instances you want to delete are on top level, you can also use "View/Select Top Level Objects". In this mode, you only select instances rather than shapes inside instances. Matthias
-
Hi @ravn, currently (with 0.27), the hidden feature is not dynamic - you can set it at the beginning, but not change it. In 0.28 you will be able to dynamically change the visibility of a parameter in a new PCell method called "callback"…