• 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. Can user assign filename to fsdb in Spectre simulation result...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 15669
  • 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

Can user assign filename to fsdb in Spectre simulation result using Spectre command option

mctang
mctang over 9 years ago

Hi

I run Spectre simulation (spectreXPS) on spice netlist using batch mode, but simulation output "fsdb" is not fixed. Is there any way to assign filename to fsdb ?

Thanks,

ManChak

  • Cancel
Parents
  • mctang
    mctang over 9 years ago

    Hi Andrew,

    I used the following command to run spectre on spice netlist. However, the fsdb filename is not fixed as <design>.fsdb, which is the default name in other simulators. Instead, spectre assigns  fsdb filename  based on simulation type (e.g. transient analysis). Does spectre allow user to predetermine fsdb file name ? 

    spectre +aps +spice -format fsdb $cellname.sp -raw ./scratchdir/dynamic -stdout run_spectre.log

    Thanks,

    ManChak

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mctang
    mctang over 9 years ago

    Hi Andrew,

    I used the following command to run spectre on spice netlist. However, the fsdb filename is not fixed as <design>.fsdb, which is the default name in other simulators. Instead, spectre assigns  fsdb filename  based on simulation type (e.g. transient analysis). Does spectre allow user to predetermine fsdb file name ? 

    spectre +aps +spice -format fsdb $cellname.sp -raw ./scratchdir/dynamic -stdout run_spectre.log

    Thanks,

    ManChak

    • 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