• 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 SKILL
  3. how to create a runobjfile to plot a family of curves by...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 13944
  • 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

how to create a runobjfile to plot a family of curves by using ocean skill.

foxest
foxest over 15 years ago

I use ocean to run the corners analysys, i can save all the corner results,but can not gather the results together to plot family of waves.

Comparing to the corner or param analysys in ADE, i found i do not create a RUNOBJFILE to combine all the results.How to create such

a runobjfile or there are other methods instead? thanks.

that is my ocean script:

ocnWaveformTool( 'wavescan )
simulator( 'spectre )
design("/home/hlq/simulation/testbench_UX2018B/spectre/schematic/netlist/netlist")
p=outfile("/home/hlq/ocean/result.txt" "w")
cor1='(
"/home/hlq/tsmc/tmodel/ss.scs"
"/home/hlq/tsmc/tmodel/ff.scs"
"/home/hlq/tsmc/tmodel/fs.scs"
"/home/hlq/tsmc/tmodel/sf.scs"
)
tmp='(-40 85)
vdd1='(2.97 3.63)
foreach(cor2 cor1
foreach(temp tmp
foreach(vdd2 vdd1
model=list(cor2 "")
if(cor2=="/home/hlq/tsmc/tmodel/ss.scs"
corn="ss")
if(cor2=="/home/hlq/tsmc/tmodel/ff.scs"
corn="ff")
if(cor2=="/home/hlq/tsmc/tmodel/fs.scs"
corn="fs")
if(cor2=="/home/hlq/tsmc/tmodel/sf.scs"
corn="sf")
modelFile(
    model ""
)
resultsDir(sprintf(nil "/home/hlq/ocean/%fV%dC%s" vdd2 temp corn ))
analysis('ac ?start "1"  ?stop "10G"  )
analysis('xf ?start "1"  ?stop "10G"  ?p "/outp"  )
analysis('noise ?start "1"  ?stop "10G"  ?p "/outp" 
  ?n "/outn"  ?oprobe ""  ?iprobe "/I2"  )
analysis('dc ?saveOppoint t  )
desVar(   "amp" 2u )
desVar(   "vdd" vdd2 )
desVar(   "cpink" 2.2n )
desVar(   "idd" 0 )
option( 'temp  "temp"
)

temp( temp )
run()
ICC = IDC("/V0/MINUS")
GAIN = dB20(value(VF("/outp") 100000000))
noise = abs((rmsNoise(1 940000000) / value((VF("/outp") - VF("/outn")) 100000000)))*1000000000
bw = bandwidth((VF("/outp") - VF("/outn")) 3 "band")
vpink = VDC("/net054")
vin = VDC("/net21")
vout = VDC("/net047")
peaking = (ymax(dB20(clip(VF("/outn") 100000000 3e+09))) - dB20(value(VF("/outn") 100000000)))
LC = bandwidth(clip(VF("/outp") 1 10000000) 3 "high")
PSRR4M = value(db(getData("/V0" ?result "xf")) 4000000)
fprintf(p,  "%dC %fV %s %fA %fnA %fHZ %fdB %fHZ %fdB \n" temp vdd2 corn ICC noise bw peaking LC PSRR4M)
)
)
)
close(p)

 

  • Cancel
Parents
  • FredWang
    FredWang over 13 years ago
    I kind of figured out a way to deal with this, in case anyone needs it. The best tool to generate the runObjFile is probably the Parametric Analysis itself. To use this, you will have to configure the parametric thing the way you normally do, but in the Ade Analyses list, only leaves dc enabled, which will cost less time for it to simulate. The runObjFile will be available in the tmp directory only after the sweep is finished.
    However, you may still need to put your results into a var-named folder structure manually.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • FredWang
    FredWang over 13 years ago
    I kind of figured out a way to deal with this, in case anyone needs it. The best tool to generate the runObjFile is probably the Parametric Analysis itself. To use this, you will have to configure the parametric thing the way you normally do, but in the Ade Analyses list, only leaves dc enabled, which will cost less time for it to simulate. The runObjFile will be available in the tmp directory only after the sweep is finished.
    However, you may still need to put your results into a var-named folder structure manually.
    • Cancel
    • Vote Up 0 Vote Down
    • 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.

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

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