• 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. Strobing Problem

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13636
  • 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

Strobing Problem

Dushan
Dushan over 15 years ago

Hi,

 I am running a pss sweep analysis and using strobing to save only certain number of points (50). Then I open the results in a table and save them in csv format for further processing. Sometimes it works perfectly, but sometimes it produces more than one point around some of the time instances (closely spaced - around 1fs or even less), so the total number of points is incorrect (e.g. 52 instead of 50). Any help with this issue?

I am running icfb sub-version 5.10.41_USR5.90.69.

 Thanks,

Dusan 

 

  • Cancel
Parents
  • Dushan
    Dushan over 15 years ago

     Andrew,

    Thanks for your answer. I am using spectre version 6.2.1.431.

    The multiple points are extremely close and the sampled signal values are essentially the same - it just confuses the scripts I am using for the processing of output data. Also, I've seen an even weirder thing happening. For example, the output is supposed to be 50x10 array (50 time points, 10 values of the swept parameter). Instead I am getting a 51x10 array where the first raw has only the first element (the rest of the raw empty), and the last raw has all the elements except the first one. I could not figure out any regularity in all this - when I change sweep range or swept variable it disappears.

     Regads,

    Dusan 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Dushan
    Dushan over 15 years ago

     Andrew,

    Thanks for your answer. I am using spectre version 6.2.1.431.

    The multiple points are extremely close and the sampled signal values are essentially the same - it just confuses the scripts I am using for the processing of output data. Also, I've seen an even weirder thing happening. For example, the output is supposed to be 50x10 array (50 time points, 10 values of the swept parameter). Instead I am getting a 51x10 array where the first raw has only the first element (the rest of the raw empty), and the last raw has all the elements except the first one. I could not figure out any regularity in all this - when I change sweep range or swept variable it disappears.

     Regads,

    Dusan 

    • 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