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
Hi Alonso,
I don't know the nature of your postprocessing. But you might consider using the DRC feature for that purpose: a DRC script can be used to process layout tool.
Within the DRC feature, you can move a layer using the "move" meth…
Hi David,
yes .. that's one solution.
Another one is to wrap a PCell in an ordinary cell and place this cell multiple times. Then this cell will change in all places in the same way.
Thanks for all your contributions and best regards,
Matthias
Hi Ryna,
0.24 was heavily reworked in the course of Python integration. I am not aware to have changed the semantics of the .lydrc format, but at least the interpreter spec got more important with Python being a new choice of a script interpreter.
…
Hi,
to be frank, I've neved had this request before.
The usual approach is to select different rules depending on additional mask layers. Since the physics of your connection must be somehow determined by the masks in a lithography process, it sho…
Hi,
does the script run from the macro IDE?
I think, in your file some of the metadata is missing. Specifically the interpreter is not given. Please try to add this information:
<?xml version="1.0" encoding="utf-8"?><…
Hi,
The following connection specification should do the job:
Conductor 1 Via Conductor 2---------------------------------------------18 14-27 3
I have tested this on a simple example.
Matthias
Hi zlim,
you can actually control the DBU the PCell uses. The layout will be converted to the DBU of the client layout when you reference the PCell library.
More precisely, the database unit is stored inside the host layout that is part of the lib…
Hi Sia,
could you give some more details about what it missing?
Is it just some cells or are those cells which are located inside a library? I assume the problem is related to the fact that you use libraries. If the missing cells are some which ar…
Hi all,
I have uploaded the new package to the server. It replaces the first one.
Thanks to kazzz for providing this package and thanks to all for this great community effort!
Matthias
Hi Micha,
The problem is buried deeply inside the Python interpreter I build against. If the one you have installed is not compatible with the one I am using (which is likely) the program will crash.
I'll try to work around this but I wish the Pyt…
Hi JP,
the layerwise geometrical functions under "Edit/Layer/.." don't preserve properties in general since they act on polygons and will not preserve the polygons in the general case. They also won't preserve the hierarchy if there is on…
Hi Masaki,
you're right. The spec says the S_BOUNDING_BOX records need to appear in the cell table, not in the cell itself.
I'll fix that in the next minor release.
Thanks for bringing this up.
Best regards,
Matthias
Hi dion,
here are the details:
KLayout detects the file format looking at the first four bytes:
* GDS: 0x00, 0x06, 0x00, 0x02
* OASIS: 0x25, 0x53, 0x45, 0x4d
The Linux "file" tool is able to detect GDS2 and OASIS files as well (I have …
Oops ... something wrong here?
This is how it's supposed to be:
klayout_vo.exe is a pure viewer application. Save functions are disabled and you cannot switch it to editor mode. This binary is not installed in the start menu but you can create you…
Hi Micha,
there is a known compatibility issue with existing Python installations. Please check whether an environment variable called PYHONPATH is set. If so, try to remove it from your system and try again.
Matthias
Hi Michael,
I am running Ubuntu 14 myself, but I don't see this issue. I'll try to reproduce it, but maybe you can try removing or renaming $HOME/.klayout/klayoutrc to start with a fresh configuration.
If that problem is still there after having r…
Hi Michael,
there is a reason for the load time difference: in viewer mode, the database will store compact shape arrays from OASIS files as such while in editor mode they are expanded. Shape arrays are no suitable basis for editing, hence editing …
Hi satya,
Thanks for your suggestions and your support.
I want to try another option which is to enable Python 2.6. But I'm kind of busy rightno so that will have to wait a little.
Thanks,
Matthias
Hi Satya,
I have published the CentOS 6 RPM's on the downloads page in between for version 0.24.2. The OSC branch has expired in between, so please use the download links from there.
But please note that the RPM provided there does not feature Pyt…
Oh yes, I see.
That's inconsistent. The property should be integer, not bool. I'll fix that in the next minor release.
Thanks for mentioning this,
Matthias
Hi Masaki,
yes, "oasis_write_std_properties" is a boolean property, so
opt = pya.SaveLayoutOptions()opt.oasis_write_std_properties = True
should work.
Doesn't it?
Matthias
Hi,
I don't know why (it's working for me) ... but "#include " is missing in pyaUtils.cc. Put it right after "#include " and your build should do.
I'm sorry I can't give you a link to any Ruby RPM. But building Ruby usually is …