Mapping Tables and PCell's TypeLayer

connan

Dear Matthias,
I'm using the mapping tables quite a lot using dummy technology profiles to open layouts an remap them.
Besides of that I'm using a simple PCell which accesses simple shapes in a salt package library and moves them to the appropriate layer via a TypeLayer attribute. Now, if I open the layout with the re-mapping technology profile, everything looks fine, but if I save the layout and re-open it, the PCells TypeLayer attributes have been switched back. Is it possible to solve this?

Best regards
connan

Matthias

Hi @connan,

I'm no sure I understand. You mean you have a PCell that for example has a TypeLayer parameter which is set to layer 17/0 and correspondingly produces shapes on layer 17/0. You save that file and then remap the layer, for example layer 17/0 to 27/0. Your expectation is that after that, the PCell produces shapes on layer 27/0?

Or in other words: that the remapping modifies the TypeLayer attribute of the PCell?

I don't think that will be possible. Layer mapping is a low-level feature while PCells are usually tied to a PDK with a fixed layer definition and no mapping.

Matthias

connan

Hi Matthias,
you exactly got the point here, but I think it's a slightly more general issue.
Think of a layout with a PCell even from the standard library. Let's say the circles' TypeLayer property is set to 1/0. If I now remap the layout with the built in mapping table, where e.g. 1/0 becomes 3/0, then everything looks fine and I guess it's that at that very moment the PCells are treated as defunct, and thus the remapping appears to be working. If I now save the file and reopen it, the circle will be on 1/0 again. So there is at least this inconsistency.
I wrote a script which also remaps all the TypeLayer properties in every PCell, which works fine. Now I'm just asking myself, whether that shouldn't be standard? At least for the TypeLayer properties which are set in the generated dialogs? Am I overlooking something here? It would be really convenient especially for textobjects and shouldn't break anything, but now it does.

BR
connan