Stats

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

Job name in adexl and directory where it will be saved

bid75

When I start a new job in ADEXL, it is named "Interactive.nnn" etc. I cannot edit that name while the run is in progress. Most of times I come back later and cannot recollect what that run was for. Is there a way to mention the name upfront before starting the job. Also at times the job gets stored in sub directories of totally different module - how to verify the saved location before starting the job.

Thanks

Bhavin

  • Andrew Beckett

    Hi Bhavin,

    If you enter (in the CIW, or in your .cdsinit):

    envSetVal("adexl.historyNamePrefix" "showNameHistoryForm" 'boolean t)

    Then when you hit the Run button a popup appears where you can type in the name you want (it adds a number to this to make it unique) and also notes as to what it is for if you want.

    Regards,

    Andrew.

  • bid75
    in reply to Andrew Beckett

    And how do you ascertain the directory where the run will be saved

  • Andrew Beckett
    in reply to bid75

    Sorry - missed that bit of the question. I've not seen it saving it under a "totally different module" - that sounds rather odd and unexpected (and I don't recall seeing that happen).

    It should be <SIMDIR>/<libName>/<cellName>/<adexlViewName>/results/data/<historyName>

    The <SIMDIR> is what is said under Options->Save as the simulation results directory, and the lib/cell/view is the lib/cell/view of the ADE XL view. Note that if it's a maestro view (for Explorer/Assembler) then the "data" in that path is replaced by "maestro" (to avoid clashes). Under the history you get numbered directories for each point, with the testName under that.

    Andrew.

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.