Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 13305
  • 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

input.scs generated from OCEAN removed some pxf analysis options

QUBOZHOU
input.scs generated from ADE and OCEAN are different. for example, input.scs from ADE ... ... pxf ( dout 0 ) pxf extrasampletimepoints=[7n] + sampledelay=[-200p] crossingdirection=fall thresholdvalue=0.55 + sampleprobe=V0 ptvtype=sampled sweeptype=absolute start=64K + stop=64M dec=30 maxsideband=10 annotate=status input.scs from OCEAN pxf ( dout 0 ) pxf thresholdvalue=0.55 sampleprobe=V0 + moduppersideband=0 outmodharmnum=1 inmodharmvec=[1] + sweeptype=absolute start=64K stop=64M dec=30 maxsideband=10 + annotate=status some options are removed somehow. the ocean script is saved from ADE/Session/Save Ocean Script.. I am using IC613.
  • Oliver LZD

    Hi, QUBOZHOU

    I have meet the same problem of missing options when generating the OCEAN from ADE(pss+pnoise simulation). Then i found the missing part in the input.scs created through ADE-Simulation-netlist-create. It may be helpful.

    However, new problem come up that i have no idea how to translate the "input.scs" back to ocean. Do you have any suggestion?



    input.scs :

    ... 

    pss  pss  fund=50K  harms=20  tstab=201u  autosteady=yes annotate =status

    pnoise pnoise start=1 stop=50M maxsideband=20 noisetype=sampled measurement=[pm0] annotate=status

       pm0 jitterevent measure=timesampled target=[x1p x1n] samplesperiod=1 samplephase=[0] samplepoints=[9u 18u 19u]

    ...

    OCEAN created:

    ...

    analysis('pss ?fund "50K"  ?harms "20"  ?tstab "201u"  ?autosteady "yes")

    analysis('pnoise  ?start "1"  ?stop "50M"  ?maxsideband "20"  ?oprobe""  ?noisetype "sampled"  ?noisetypeUI ""  ?noisetypeUI1 "sampled(jitter)"  ?sampleratio ""   )

    ...

    (pss successed  but pnoise failed because of "ERROR(SPCRTRF-15462): No jitter event measurement is defined")

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.