atork
About
- Username
- atork
- Joined
- Visits
- 26
- Last Active
- Roles
- Member
Comments
-
@Weiling_Zheng The above is just Calibre report. That's not the database. Also, I advise you to remove this as I believe that's a violation of software terms.
-
@Matthias I have tried using "-without-qt" and I got this: In file included from ../../../src/tl/unit_tests/tlFileSystemWatcherTests.cc:24:../../../src/tl/tl/tlFileSystemWatcher.h:32:10: fatal error: QObject: No such file or directory #in…
-
@Matthias Could I use deep and tiling together?
-
@Matthias I believe it should be defined by the user using layer derivations just like (x) tool. Building an entire custom device is hectic.
-
Thanks @Matthias for the detailed response. But here is our findings: * Tested .forget but didn't do much. It didn't clear memory that much anyhow. * We generate the ruby rule deck. And we analyze dependencies to make sure we have proper order but…
-
BTW the reason behind my request is a trial to increase the capacity and speed of the current engine. We are struggling to use Klayout on medium sized designs. It takes a lot of Memory/time to complete.
-
Hi @Matthias , That's great news. Looking forward to seeing this it would definitely help. But I think mine is different, just to clarify my request, I only want the DRC/LVS sections only from klayout without the rest at that point. Looking at the…
-
@sebastian we tried sh build.sh -without-qt And it still required mutliple Qt libraries to exist and the build failed.
-
@sebastian I tried all of that. Actually, we have a full rule deck developed that runs without GUI. But we are still seeing a possible improvements if we could isolate the Ruby code manually with all required libraries code outside of klayout main p…
-
@dick_freebird We only need a limited number of libraries that are part of the base DRC check. It makes it easier for us to contribute in klayout code base. Yes, I know we would duplicate that code in separate repo. But we could resolve that to by u…
-
@Matthias FYI, we don't need a GUI for such tool. Only command line would be the best.
-
Talking about this: https://www.klayout.de/doc/code/class_LayoutToNetlist.html
-
@Matthias , I forgot to mention that it takes too much memory as well not sure why.
-
Also, the metal can be connected anywhere not necessarily above the NWell.
-
Hi @Matthias , It could be any stamping not necessarily MOS devices. For example an ntaps, you can't have 2 ntaps on the same NWELL that connected to different nets. Assume now that we don't allow connectivity through NWELL for example. Regards, A…
-
Hi @Matthias , I'm still seeing issues with my layout. Is it possible that you share the example gds file that you are using above. I'll try to duplicate the issue for you on your design. Regards, Amro
-
Hi @Matthias , I want to avoid to add a device statement in DRC. And I want to check stamping. And yes, we use netlist command in DRC. And we know how to map the netlist info to polygons like l2n database. But the problem we are facing is hard to …
-
Hi @Matthias , We tried to use the command above but we got the following: ERROR: In my.drc: 'connect': The layout has multiple top cells in Layout::top_cellERROR: 'connect': The layout has multiple top cells in Layout::top_cell in Executable::exe…
-
Hi @Matthias , Thanks for your response. Yes, it makes sense. But I want to avoid that in DRC rule. as much as possible. That's a DRC rule deck. Not sure how this will work. Regards, Amro