Indeed, I've updated the scripts so it's easy to p...
# ieee-sscs-dc-23
a
Indeed, I've updated the scripts so it's easy to perform the process. • Store the GDS on the unzipped folder
CMC_drc_results_...
• run
make raw
and store the drc results with the same name but adding
.lyrdb
as extension (at the end is like
ascii.txt.lyrdb
). • run
make
Replace
GDS
variable with the correct gds name
In my case, I have to rename my top cell "LTC2" to "top".
The IO.0_deck drc indicates a subsection of the COMP area, should I cover only that o the entire COMP? In the image all the comp is covered with
Latchup_MK
, Not just the highlighted area.
a
@Amro Tork @Tim Edwards
g
So, just adding the
Latchup_MK
does not fixed the IO.0_deck right ?
a
Nono, I was asking if the Latchup could fix the drc problem. I'm not sure if it works or not. With atif we have our GDS with the layer, waiting for CMC results
👍 1
g
@aquiles viza I wasn't able to open the CMC-DRC result your way, the scripts didn't work on my pc. I manage to go to
Marker Database Browser
direct on klayout and open directly the
IDDMIMS3.strm.ascii.txt
file. But the errors position came a little bit off from the gds itself, around 15um off.
a
Using the
Marker Database Browser
is an option too. I'm not sure why the results could be moved, I found that LTC2 gds was analyzed with the name
top
, so maybe your design was modified too. @Juan Sebastian Moya Do you think LTC2 and Bracolin GDS were edited on CMC side?
g
I had to modify the TOP to "top" also, to use the Marker Database
a
If you move the TOP design 15um. Will it work? It seems weird that the script did not work on your pc. If you want we can make a meeting