Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 4867
  • 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

skill code to turn on/off grid

Karev11

Hi,

I have two SKILL code related questions in virtuoso:

In layout, what is the command that controls ON/OFF of Palette/Grids/Tracks and Palette/Grids/Grids, I tried to guess based on command list from Options/Bindkey editor/Layout, but could find corresponding ones. 

In Viva waveform viewer, what I had to do almost every time is:

- Graph Properties/General/Color/Background: change to white

- Axis Properties/General/Font/Color: Font Style change to Bold; Size change to 12

- Trace Properties/Type/Style: change to Medium

It'll be very helpful if we can figure out command for those, so that they can be set as default in .env file I guess.

btw, apology for posting in the wrong section earlier, and couldn't find a "delete post" option there. 

Thanks,

Kevin

Parents

  • Kevin,

    I deleted your duplicate post; the reason it didn't get answered was almost certainly not because it was in the wrong forum but because nobody got to it yet (not helped by the fact you've asked two completely separate questions in the same thread).

    Anyway, for the palette question, functions such as:

    pteSetVisible("Grids" t "Grids")
    pteSetVisible("Tracks" t "Grids")
    pteSetVisible("Tracks;Metal2" nil "Grids")
    pteSetVisible("Grids;Placement Grid" nil "Grids")

    The first two turn on the Grids and Tracks as a whole (if the second argument was nil it would turn them off) and then the second pair of functions show how to turn off (or on) a specific track or grid.

    To set the defaults in ViVA:

    envSetVal("viva.rectGraph" "background" 'string "white")
    envSetVal("viva.axis" "font" 'string "Helvetica,12,-1,5,75,0,0,0,0,0")
    envSetVal("viva.trace" "lineThickness" 'string "medium")

    Note that if you plot signals from ADE the thickness may not be honoured because it uses the colour and thickness from the packet for the layer purpose pair y0-y9 so that the schematic can be probed with the same colour as the graph. Note the above is the .cdsinit (SKILL) way of setting the variables; you could also put them in the .cdsenv file without the envSetVal(), without the quotes on the first two arguments (but remaining on the last argument) and without the single quote before 'string - e.g.

    viva.rectGraph background string "white"

    Regards,

    Andrew.

Reply

  • Kevin,

    I deleted your duplicate post; the reason it didn't get answered was almost certainly not because it was in the wrong forum but because nobody got to it yet (not helped by the fact you've asked two completely separate questions in the same thread).

    Anyway, for the palette question, functions such as:

    pteSetVisible("Grids" t "Grids")
    pteSetVisible("Tracks" t "Grids")
    pteSetVisible("Tracks;Metal2" nil "Grids")
    pteSetVisible("Grids;Placement Grid" nil "Grids")

    The first two turn on the Grids and Tracks as a whole (if the second argument was nil it would turn them off) and then the second pair of functions show how to turn off (or on) a specific track or grid.

    To set the defaults in ViVA:

    envSetVal("viva.rectGraph" "background" 'string "white")
    envSetVal("viva.axis" "font" 'string "Helvetica,12,-1,5,75,0,0,0,0,0")
    envSetVal("viva.trace" "lineThickness" 'string "medium")

    Note that if you plot signals from ADE the thickness may not be honoured because it uses the colour and thickness from the packet for the layer purpose pair y0-y9 so that the schematic can be probed with the same colour as the graph. Note the above is the .cdsinit (SKILL) way of setting the variables; you could also put them in the .cdsenv file without the envSetVal(), without the quotes on the first two arguments (but remaining on the last argument) and without the single quote before 'string - e.g.

    viva.rectGraph background string "white"

    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.