Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 6967
  • 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

Warnings about non-existing dependent expressions in ADE-L

MtHopper

I am experiencing the same problem as what is discussed in the locked discussion linked below. I was unable to find another related discussion that is not locked to reply to, so any suggestions would be greatly appreciated.

community.cadence.com/.../ade-l-generates-grf-files-with-non-existing-expression-definitions

  • ShawnLogan

    Dear MtHopper,

    Hi! I'm having an annoying issue with some states in ADE-L. For some reason, some old expression definitions are being held somehow somewhere (even if they don't exist at all in the outputs list), and when I save any waveform files (.grf) these definitions are included on them, causing lots of warning to appear each time I load these .grf files.

    I actually filed a Cadence SR regarding this issue many years ago and am quite familiar with the issue. Basically, Cadence acknowledged the issue but did not offer a solution. The expressions are contained in the ".grf" file as the prior posts noted and are carried on as "baggage" (my expression) even if a new ViVA window is saved to a new ".grf" file that does not use the expression or waveform(s). I requested on several occasions some documentation of  a ".grf" file syntax as I often edited a ".grf" file to change the results from a simulation in a different database. I was told the format of a ".grf" file is considered proprietary and hence there was no plan to document it for general use.  In short, I do not have a suggestion as to how to remove the old expressions that will not result in a corrupt ".grf" file. I can only add the result of submitting the SR.

    Shawn

  • Andrew Beckett
    in reply to ShawnLogan

    Bear in mind too that ADE L is obsolete; it is no longer sold as a product and you should move to ADE Explorer; that wouldn't have this issue.

    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.