Wavescan Ignoring Environment Variables

Discussion in 'Cadence' started by Jake, Jul 23, 2010.

  1. Jake

    Jake Guest

    Hello,

    Does anybody know why Wavescan ignores envSetVal commands? If I query
    an environment variable using envGetVal, it will show up as the value
    that I just set, but then the plot will still just use the default
    values.

    Thanks,
    Jake
     
    Jake, Jul 23, 2010
    #1
    1. Advertisements

  2. Jake wrote, on 07/23/10 23:16:
    Jake,

    Two reasons:

    1. wavescan is a separate process, and so not everything will be passed across
    the interface from DFII. wavescan will read the .cdsenv itself, so .cdsenv
    settings will usually have an influence. If you call envSetVal() in the CIW, all
    it affects is DFII itself, not the separate wavescan process
    2. Some things are overridden by ADE, if plotting from ADE. For example colours,
    line styles, thicknesses and so on.

    Regards,

    Andrew.
     
    Andrew Beckett, Jul 26, 2010
    #2
    1. Advertisements

  3. Jake

    Jake Guest

    Hi Andrew,

    Thank you for the insight, as usual.

    I'm actually starting up the tool from OCEAN via a terminal. Am I to
    take it that Wavescan also ignores the environment settings that are
    set from the OCEAN session? Where do you suggest is the best place to
    set these values?

    Thanks,
    Jake
     
    Jake, Jul 26, 2010
    #3
  4. Jake wrote, on 07/26/10 14:50:
    Jake,

    In ~/.cdsenv

    Or you could put them in ./.cdsenv and then use:

    setenv CDS_LOAD_ENV addCWD

    Running "ocean" from a terminal is essentially the same as running "icfb" in
    that it is the main DFII executable, and wavescan (the graph part) is a separate
    process.

    Regards,

    Andrew.
     
    Andrew Beckett, Jul 27, 2010
    #4
  5. Jake

    Jake Guest

    Hi Andrew,

    I have tried that, but to no avail. A statement such as:

    wavescan.graph majorForeground string "green"

    placed in ~/.cdsenv is also ignored, with no warnings or messages
    anywhere stating why.

    Thanks,
    Jake
     
    Jake, Jul 27, 2010
    #5
  6. Jake

    I-F AB Guest

    Hi,

    I haven't used wavescan but perhaps you can check your local directory
    where you are starting the tools - is there a .cdsenv file there
    already (i.e. ./.cdsenv)?
    It might be overriding the .cdsenv in your home directory (i.e.
    ~/.cdsenv) .
    These things seem trivial but sometimes that's just what's happening.

    Best regards,
    I-FAB
     
    I-F AB, Aug 5, 2010
    #6
  7. Jake wrote, on 07/27/10 20:25:
    Hi Jake,

    The problem is probably because of your color scheme setting. In wavescan, go to
    Frame->Color Schemes and select "Default".

    There's no cdsenv for Color Scheme, but it is persistent. So if you quit
    wavescan and restart, it should remain in the "Default" color scheme (this is
    stored in ~/.ws_state).

    If you have a different color scheme selected, that overrides various colour
    settings, including the majorForeground setting you have set above.

    I tried this, and I was successfully able to set the majorForeground grid to
    green or any other color I chose.

    Regards,

    Andrew.
     
    Andrew Beckett, Aug 5, 2010
    #7
  8. Jake

    Jake Guest

    Andrew,

    Awesome, that suits my needs!

    Thanks,
    Jake
     
    Jake, Aug 6, 2010
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.