Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 15080
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VI Editor Script

xv12
I am using the function dbWriteSkill to dump the layout to a file and want to modify to just stretch the length and everything contact metal implant will also stretch.
I want to use the vi editor to modify.  Does anyone have a quick way to do it. For me I have to delete one by one and it take a longtime  
Below is the partial dump file
dbD_0xcd1f768 = dbCreatePolygon(dbD_0xcc0c42c list(16 252)
 list(2.650000e+01:2.930000e+01 2.240000e+01:2.930000e+01 2.240000e+01:7.000000e+00
      7.000000e+00:7.000000e+00 7.000000e+00:2.520000e+01 2.240000e+01:2.520000e+01
      2.240000e+01:2.930000e+01 2.900000e+00:2.930000e+01 2.900000e+00:2.900000e+00
      2.650000e+01:2.900000e+00 ) )
And this is what I want to change.
 (pcLayer = 16)
 (pcPurpose = "drawing")
 (pcInst = dbCreatePolygon(pcCellView
  list(pcLayer pcPurpose)
  list((26.5:(29.3 + l_float0offset))
      (22.4:(29.3 + l_float0offset))
      (22.4:7.0)
      (7.0:7.0)
      (7.0:(25.2 + l_float0offset))
      (22.4:(25.2 + l_float0offset))
      (22.4:(29.3 + l_float0offset))
      (2.9:(29.3 + l_float0offset))
      (2.9:2.9)
      (26.5:2.9)
  )
Parents

  • You're mixing terminology all over the place here, which makes it very unclear. The example you gave in the original post looked like pcell code (i.e. what you were changing to, with all those pcCellView references etc), but yet you say you don't want to create a pcell. Then in this last append you say you want to "form a simple pcell". It's no wonder nobody understands what you're trying to do!

    As has been said consistently, dumping to SKILL and editing the SKILL is not a terribly efficient way of stretching some shapes. It would be easier to write some SKILL code to identify the shapes you want to edit (maybe even select them in the layout editor) and then have SKILL code manipulate the points for those shapes.

    If you're asking a question about how to change a floating point number in the dumped SKILL code in vi to a number without an exponent, then that's going to be quite hard. However, getting rid of the multiple zeros is just a matter of doing:

    :g/0*e/s//e/g

    If you want to preserve one 0, use:

    :g/0+e/s//0e/g

    Regards,

    Andrew.

Reply

  • You're mixing terminology all over the place here, which makes it very unclear. The example you gave in the original post looked like pcell code (i.e. what you were changing to, with all those pcCellView references etc), but yet you say you don't want to create a pcell. Then in this last append you say you want to "form a simple pcell". It's no wonder nobody understands what you're trying to do!

    As has been said consistently, dumping to SKILL and editing the SKILL is not a terribly efficient way of stretching some shapes. It would be easier to write some SKILL code to identify the shapes you want to edit (maybe even select them in the layout editor) and then have SKILL code manipulate the points for those shapes.

    If you're asking a question about how to change a floating point number in the dumped SKILL code in vi to a number without an exponent, then that's going to be quite hard. However, getting rid of the multiple zeros is just a matter of doing:

    :g/0*e/s//e/g

    If you want to preserve one 0, use:

    :g/0+e/s//0e/g

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.