Stats

  • Locked Locked
  • Replies 31
  • Subscribers 148
  • Views 29611
  • 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

How to change via level with skill in IC6

Eric L14

 In IC6, I have a bindkey which change via level (via1 to via2) . Main part of the code is:

; Current selected via
viaToBeChanged=car(geGetSelSet())

; new via identifier
newVia=dbOpenCellViewByType( technName viaName "layout" nil "r")
if( newVia then
  viaToBeChanged~>master=newVia
)

Do you know how doing the same thing in IC6 ?

Thanks in advance

Eric

Parents

  • A bit tricky here because we have two interleaved threads (I think it might be beyond my moderator skills to sort out the mess and separate them). So let me answer VaughnR's questions first, and then come back to Antonios.

    Firstly, some examples and more info in some solutions. This solution was created before dbCreateStdViaVariant was created (I think). And this solution talks about using dbCreateStdViaVariant.

    Personally I find the API for dbCreateStdViaVariant a bit odd. The idea of a viaVariant is that it is a variant of a normal via, but with particular values for rows and columns, enclosures, spacings etc. So it's like a template that you can reuse. From the create via form, you can save away a via variant, and then when you use it, you don't have the opportunity to change any of the parameters. With the API however, you have to specify all the parameters, so I can't see much point in using a viaVariant over the source via! I'm going to ask R&D about this. If dbCreateStdViaVariant had optional arguments after the  viaVariantName (or viaDefName) then I could understand it - but it doesn't - they're all required arguments.

    Now, for the cutPattern. I wrote some SKILL to do what you want - to encode the cut pattern for you.

    Regards,

    Andrew.

Reply

  • A bit tricky here because we have two interleaved threads (I think it might be beyond my moderator skills to sort out the mess and separate them). So let me answer VaughnR's questions first, and then come back to Antonios.

    Firstly, some examples and more info in some solutions. This solution was created before dbCreateStdViaVariant was created (I think). And this solution talks about using dbCreateStdViaVariant.

    Personally I find the API for dbCreateStdViaVariant a bit odd. The idea of a viaVariant is that it is a variant of a normal via, but with particular values for rows and columns, enclosures, spacings etc. So it's like a template that you can reuse. From the create via form, you can save away a via variant, and then when you use it, you don't have the opportunity to change any of the parameters. With the API however, you have to specify all the parameters, so I can't see much point in using a viaVariant over the source via! I'm going to ask R&D about this. If dbCreateStdViaVariant had optional arguments after the  viaVariantName (or viaDefName) then I could understand it - but it doesn't - they're all required arguments.

    Now, for the cutPattern. I wrote some SKILL to do what you want - to encode the cut pattern for you.

    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.