• 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. Cadence ADEXL: how to merge troubleshot point with rest...

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 126
  • Views 18999
  • 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

Cadence ADEXL: how to merge troubleshot point with rest of montecarlo data

spectrallypure
spectrallypure over 12 years ago

Hello! I am having problems plotting the histograms of my monte carlo runs. Sometimes (I suspect due to license timeouts) the simulation of some points in the run "kind of" fails (i.e., they are not flagged as failed, but all their associated evaluated/measured quantities are zero!). These points lead to wrong histograms, since the zero values are taken into account for the plotting.

If, however, after the whole monte carlo run is over I use the option "[right-click] Troubleshoot point" on these failed points, they all run fine. The problem is that the troubleshot results for these points are not integrated with the rest of the monte carlo run, so I still get ill histograms. So my question is, how can I tell adexl to merge the troubleshot points' results with the rest of the original results, so as to replace the old zero-valued entries?

Thanks in advance for any help/ideas/comments.

Cheers,

Jorge.

P.S. I naively attempted to fool adexl by manually copying the troubleshot results into the old point's data directory, but it didn't work; I guess I'm still lacking  a way to make adexl reload the data from the disk... how could I force this? (yes, I tried closing everything and reopening, but it doesn't seem to read the overwritten data!). 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Hi Frank,

    It's definitely been changed. Maybe support.cadence.com is showing the "reported" severity of the master CCR rather than the Cadence-assigned severity (although I'm not sure how) - or maybe it's just a data synchronization issue:

      ---------------------------------------------------------------------------
        CCR: 704700         
      Title: Ability to merge two run results
      ---------------------------------------------------------------------------
           State: Inactive      Inactive Reason: BK-Backlog 
        Req Type: E)nhancement     Rep Req Type: E)nhancement 
        Severity: 1                Rep Severity: 2           
         Urgency: D                 Rep Urgency: D           

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 12 years ago

    Seems to have been a data synchronization issue: now I also see "Severity: Important" for this CCR.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
<

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.

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

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