• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. ADE Assembler – managing a large number of output expressions...

Stats

  • Replies 1
  • Subscribers 129
  • Views 69
  • Members are here 0

ADE Assembler – managing a large number of output expressions (file-based approach?)

baltaci
baltaci 21 hours ago

Hello,

I am working with ADE Assembler and in many of my tests I define a large number of output expressions. These outputs are often Calculator-based expressions, and some of them are quite complex.

As the number of outputs increases, the Outputs setup in ADE Assembler becomes difficult to manage:

  • The Outputs table gets very long

  • It becomes hard to read, edit, and maintain

  • Reusing the same set of outputs across multiple tests is cumbersome

What I would like to achieve is a cleaner and more scalable workflow, for example:

  • Defining most (or all) output expressions in an external text file

  • Introducing this file into a specific ADE Assembler test

  • Having the test automatically evaluate all those expressions as outputs, in addition to any outputs still defined directly in the Outputs setup

Ideally, this would allow:

  • Centralized maintenance of output expressions

  • Easy reuse across tests

  • Less manual interaction with the Outputs GUI

My questions are:

  1. Is there a recommended and supported way in ADE Assembler to define output expressions externally (file-based)?

  2. If so, is there a step-by-step guideline describing:

    • Where such a file should be introduced in ADE Assembler

    • How it is associated with a specific test

    • When it is evaluated during the run

    • How to access them after the simulation
  1. Where can I find the official syntax for writing these output expressions?

  2. Is it possible to use Calculator expressions (or Calculator-style syntax) in such a workflow, since this is already the primary way I define outputs today?

Any guidance, documentation references, or best-practice workflows would be greatly appreciated.

Thank you.

Kind regards,

Can

  • Cancel
  • Sign in to reply
Parents
  • Andrew Beckett
    Andrew Beckett 21 hours ago

    Can,

    You have the ability to save and load outputs in both Explorer and Assembler. In Assembler there's a save icon above the output table which will save the outputs to a CSV and you can then see the format. It supports all the outputs and expressions as normal and then after editing you can import them back in again. In fact, in IC25.1 ISR3 there's an edit button which will save, launch an editor and then re-load after the editor is closed.

    That's the simplest. There's nothing really to support having a file of external expressions which is kept as an external file (well, you could add an OCEAN script output, which can generate multiple outputs and have them appear in the output table - that would be another possibility).

    I'd probably just use the export/import (or save/load) approach.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 21 hours ago

    Can,

    You have the ability to save and load outputs in both Explorer and Assembler. In Assembler there's a save icon above the output table which will save the outputs to a CSV and you can then see the format. It supports all the outputs and expressions as normal and then after editing you can import them back in again. In fact, in IC25.1 ISR3 there's an edit button which will save, launch an editor and then re-load after the editor is closed.

    That's the simplest. There's nothing really to support having a file of external expressions which is kept as an external file (well, you could add an OCEAN script output, which can generate multiple outputs and have them appear in the output table - that would be another possibility).

    I'd probably just use the export/import (or save/load) approach.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information