• 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. Regarding Smoothness in transient analysis

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15486
  • 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

Regarding Smoothness in transient analysis

RFStuff
RFStuff over 11 years ago

 Dear All,

I created a verilogA module.

What it basically does is as below:-

It is a simple sine wave generator. 

I stored the sine wave  time & amplitude in a text file for one period of the sine wave.

The verilog A code reads the file and generates the sine wave for the entire transient simulation time.

But the problem is:-

If I am not using the strobeperiod, the curve is NOT smooth at all.

But when I use stobeperiod=1ps then it becomes smooth.

I was thinking that the  transient simulation will be evaluated at each time point stored in the file.

Can anybody please tell why this is happening.

Kind Regards,

  • Cancel
Parents
  • skillUser
    skillUser over 11 years ago

    Hi RFStuff,

    The simulator will only place timesteps that are sufficient to resolve the equations, not necessarily enough that the sine wave looks like a sine wave.  One way to help the simulator take more timesteps is to use the bound_step() function - this should be a little nicer to the simulator (than strobeperiod) as it still has flexibility on the time points, but now they are limited to a maximum time between steps. Work out how many samples/points you wantper cycle and work out the max timestep from there.

    I hope that this helps.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 11 years ago

    Hi RFStuff,

    The simulator will only place timesteps that are sufficient to resolve the equations, not necessarily enough that the sine wave looks like a sine wave.  One way to help the simulator take more timesteps is to use the bound_step() function - this should be a little nicer to the simulator (than strobeperiod) as it still has flexibility on the time points, but now they are limited to a maximum time between steps. Work out how many samples/points you wantper cycle and work out the max timestep from there.

    I hope that this helps.

    Regards,

    Lawrence.

    • 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