When You Desperately Need the Numeric ADE Outputs in Selectable Text

You've just done a simulation using the Assembler Debug Environment (the good old ADE-L) and now you want to capture the numbers as text so you can put them in a spreadsheet, or whatever..

In ADE, Outputs > Export.. dump as a CSV file

Then, in a terminal:

perl -n -e 'if( /^([^,]+),expr,([^,]+),t,.+,t,t?$/ ){ $op = $1; $opp = $1; $ex = $2; $op =~ s/\s/__/g; print "$op = $ex\n";  print q{printf("} . $opp . q{,%s\n",aelSuffixNotation(}.$op.q{))},"\n"; }' /tmp/desired_outs.csv > /tmp/outputs.il

After that, you just (in your CIW)

loadi "/tmp/outputs.il"

Let's break all of that down:

The regex in perl is looking for expressions (you don't want signals, etc) : "expr", but it's also looking for those that are set to "Yes, plot".



Comments

Post a Comment

Popular posts from this blog

Plotting Device Parameters (gm, vdsat, etc) Vs Time or Temp

Image
I feel like this has gotten more complicated. I think it might have been easier 10 years ago. Then again, I could be w. Go to resource: How to save and plot operating point parameters for Spectre simulator from ADE Explorer/Assembler In Explorer, you go to Outputs > To be Saved > Select OP Parameters Now, the schematic window is active and you can click on instances and each gets highlighted as you do. These get populated in the Assembler Outputs Setup You will see that the "Type" is not signal but oppoint. If you click on the Details field, it splits into two - the /whatever/deviceName is on the left, and on the new field on the right, you can enter parameters appropriate for that device, like vdsat, vth, cgs, etc.  The UI is very poor, but, on the right of this field is a button you can actually click to choose from a list. It'll even run a sim if necessary! If you want these plotted, you have to check the box to the right under the Plot column.
Read more

When You Want to Get Cycle-to-Cycle Jitter at PLL Output Due to the Reference Oscillator

Image
Caution - the script does not provide the correct result. You expect cycle-to-cycle to be a high-frequency phenomenon - and therefore, to not depend on the oscillator phase-noise or jitter. But the script will show a large value for c2c jitter on the PLL output. If you can figure it out, please post/comment. Designers Guide : Phase Noise and Jitter prediction , by Ken Kundert Converting Phase Noise to Cycle-to-Cycle Jitter in a PLL When designing or analyzing phase-locked loops (PLLs), one key metric of interest is the RMS cycle-to-cycle jitter at the output. Given phase noise data (typically in dBc/Hz) for the reference oscillator, how do we estimate the jitter after the PLL processes it? 🎯 Goal Estimate RMS cycle-to-cycle jitter (in seconds or picoseconds) at the output of a PLL , based on: Measured or simulated phase noise data (dBc/Hz vs. offset frequency) PLL dynamics: natural frequency ( fn ), damping ratio ( ζ ), divider ratio ( N ) Carrier frequency ( fc ) ...
Read more

HIdden States in Your Behavioral Model

Image
Rewrite the module to remove the hidden state or if you confirm this hidden state will not affect the simulation result, you can ignore those hidden states in RF analysis by adding attribute 'ignore_hidden_state' before the module declaration. For example,  (* ignore_hidden_state *) module moduleA Yes, that's the exact syntax you need to use - that line works so much magic. It's strange that Cadence would offer behavioral models to customers in its ahdlLib library that aren't "ready to roll" in terms of NOT having hidden states. https://designers-guide.org/analysis/PLLnoise+jitter.pdf https://community.cadence.com/cadence_technology_forums/f/rf-design/26712/how-to-avoid-hidden-state-in-veriloga-model-for-spectrerf
Read more