Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 7789
  • 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

Rerun History in Assembler with more points enabled while re-using previous results?

david1110

I ran a long sweep of multiple variables on a single test in Assembler and disabled about half of the points in the Run Preview tab. After running I decided I want to enable all the points and have them all available in a single history. The first run of about half the points already took about a day to simulate, so I'd rather not have to re-run those points.

I've tried setting the history item as a reference history, but it seems to basically ignore it when I do and re-runs the points anyway. I also tried enabling every point and starting a run then immediately cancelling it to create a history item, then tried using "Merge And Load To Active" to merge it with the original run, but when I do that it just immediately cancels itself after it starts. When I try previewing the merged run, the "History" and "Point Status" columns only show "-" (dashes), indicating that those points don't match any of the histories I'm trying to merge, despite the fact that I haven't changed anything else in the setup (I even tried loading the original history's setup to active before starting).

I've looked through both the documentation for the rapid adoption kit "Reference History and Merge History in ADE Assembler" and the documentation for Assembler itself. (In fact, I'm struggling to even find any explanation of reference histories in the Assembler documentation, though merging histories is discussed). As far as I can tell, I'm not doing anything significantly different from what is described in either than those.

Other points that may or may not be relevant:

  • I'm running only one test and many of the variables are set there
  • Some variables are set as global variables, including all the variables that are being swept
  • I'm running only one corner, which is overriding a few variables (none of the ones being swept)
  • Virtuoso version is ICADVM20.1-64b.500.27

Any help or advice would be appreciated!

  • Dear david1110,

    I understand your basic issue, but for me anyway, there are many settings that you have not included that might help me provide a more definitive answer. A couple of questions come to mind that may be obvious to you, but without knowing your specific steps, I was not sure and felt I should mention them.

    1. In the reference history panel, did both select and add your history item as a "selected history" and make sure the radio button "Copy results and run remaining points" was selected?

    2. Did the Run simulation icon change from green to blue prior to starting your run?

    Shawn

  • in reply to ShawnLogan

    Thanks for the reply!

    1. Yes, I added the history item as a "selected history". And yes, "Copy results and run remaining points" was selected. I also tried with and without "Ignore Setup Changes" selected.

    2. Yes, the Run Simulation icon changed to blue.

    David

  • in reply to david1110

    Dear david1110,

    Thank you for reading my comments and including your added information. If your attempt to re-run the former test with additional sweeps consistently results in re-simulating those sweep points you simulated in your initial run (say in history0), then my guess is the set-up or netlist for this run must differ in some way from the netlist used in history0.

    1. Did you try checking the "Ignore Setup Changes" in the Reference History GUI.

    2. Did you compare the input.scs file for a corner from history0 with the newly created netlist for the same corner? In essence, re-create the netlist for a corner you have already run and compare its input.scs with the input.scs for the same corner in history0.

    Once again, without all the details, I am only guessing as to why it may not be working for you. A possible troubleshooting  exercise is to use the test case in the RAK you referred to and make sure your results are the same as those in the RAK. This might show you a step you overlooked or, possibly, an issue with the version of the tools you are using. 

    Sorry I can not provide more specific guidance - but I just don't have all the details of the your process and setup!

    Shawn

  • in reply to ShawnLogan

    This worked fine for me - although I was running with ISR32 rather than ISR27. 

    I suggest you contact customer support (submit a support case after logging in) so that we can take a look at this with your setup. That's what customer support is for...

    Andrew

  • in reply to david1110

    Thanks Shawn and Andrew. Knowing at least that this should work is helpful in itself. For this case I ended up just re-running the full sweep. If I get some time soon I may try going through the RAK, and if I can't get that working I'll contact customer support.

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.