Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 13821
  • 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

options to get commands in layout virtuoso ic615

vijayrajR15

Hi,

 Consider i have done operation like placed a mos in layout and made connections.. Now i need commands for that operation. In the sense the command for each step in ciw window or file which has all the previous commands. That should be similar to "viewLog" command in cadence soc encounter 14.1..  Please help..

 

Thanks

vijay

Parents

  • All the values provided should also be in the log file - so that it's replayable. 

    However, you generally shouldn't write SKILL code using exactly the same functions that appear in the log file. These are the "human interface" versions of the functions, which accept mouse clicks etc (you'll see a record of mouse clicks and form interactions in the log file). What you should be using are the "procedural interface" versions, which accept a number of arguments.

    So you might see (say) leHiCreateRuler in the log file, but should be using leCreateRuler in SKILL code. From the SKILL finder (the quick reference), you can see the difference in arguments:

    leHiCreateRuler(
    [ w_windowId ]
    )
    => t | nil
     
    Opens the Create Ruler form, which lets you create a ruler in
    the specified window. If w_windowId is not specified, the current
    window is used.

    leCreateRuler(
    d_cellViewId
    l_points
    )
    => t | nil
     
    Creates a ruler in cellview d_cellViewId with vertices at the
    coordinates listed in l_points. 

    Some functions don't have non-hi equivalents, and some would use lower level functions instead for that purpose (e.g. the db.* functions).

    More info on these functions in the documentation (cdnshelp), with cdsFinder providing a quick reminder of the purpose and arguments for the functions.

    Regards,

    Andrew.

Reply

  • All the values provided should also be in the log file - so that it's replayable. 

    However, you generally shouldn't write SKILL code using exactly the same functions that appear in the log file. These are the "human interface" versions of the functions, which accept mouse clicks etc (you'll see a record of mouse clicks and form interactions in the log file). What you should be using are the "procedural interface" versions, which accept a number of arguments.

    So you might see (say) leHiCreateRuler in the log file, but should be using leCreateRuler in SKILL code. From the SKILL finder (the quick reference), you can see the difference in arguments:

    leHiCreateRuler(
    [ w_windowId ]
    )
    => t | nil
     
    Opens the Create Ruler form, which lets you create a ruler in
    the specified window. If w_windowId is not specified, the current
    window is used.

    leCreateRuler(
    d_cellViewId
    l_points
    )
    => t | nil
     
    Creates a ruler in cellview d_cellViewId with vertices at the
    coordinates listed in l_points. 

    Some functions don't have non-hi equivalents, and some would use lower level functions instead for that purpose (e.g. the db.* functions).

    More info on these functions in the documentation (cdnshelp), with cdsFinder providing a quick reminder of the purpose and arguments for the functions.

    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.