It looks like you're new here. If you want to get involved, click one of these buttons!
Hello, thank you for the great tool!
I've been running through an issue where I'm trying to optimize an xor script used for huge layouts using TilingProcessor I used the script in the documentation and it is really fast, but I was wondering how I could output these layers into a new gds file (I added a loop that gets all layers from the 2 layouts and queues them to do the xor). I tried using this function and then doing a simple layout.write("output.gds")
after the loop but it ends up with an empty layout.
Any suggestions on how to write the output one by one? maybe from inside the queue script itself?
Comments
@marwaneltoukhy The script inside the tiling processor should not write anything. In order to receive something on the output, you need to call the "_output" function inside the script.
The TilingProcessor description gives an example.
Maybe this discussion is easier if you paste code.
Matthias
@Matthias The code for xor:
@marwaneltoukhy The script is basically correct, but it's a bit weird: are you trying to use DRC or is that a basic Ruby API script?
When I rewrite it to Ruby, the script looks like this:
And for me it seems to work.
Inside DRC you don't need to implement the tiling yourself. DRC wraps it for you. Just say:
Matthias
@Matthias Thanks for your clarification, but the
o.write("output.gds")
in the first script actually doesn't output anything in theoutput.gds
file@marwaneltoukhy No, sorry, I just confirmed that the Ruby script I showed works (I added the missing '#' at the beginning).
But maybe your input files are identical? In this case the XOR output is empty. That's how XOR says the files are the same.
Matthias