• 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
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    This is a consequence of spectre supporting multiple named analyses of the same type. Each can have their own separate result database.

    So for example if my netlist looks like this:

    //

    R1 (n1 n2) resistor r=1k
    C1 (n2 0) capacitor c=1p
    V1 (n1 0) vsource type=pulse val0=0 val1=2 rise=1n width=10n period=20n

    mytran tran stop=1u
    yourtran tran stop=2u

    And I run with -f fsdb (the netlist above is in spectre syntax - so you can see I have two differently named transient analyses), I get:

    UNIX> ls myresults.raw/
    logFile mytran.tran.fsdb yourtran.tran.fsdb

    The filename has the name of the analysis instance, the type of analysis (because there could be other types) and the format as part of the name. You can't change the name of the file to match the design unless the instance name of the analysis matches the design name.

    The reason for this is that each result directory is intended to be unique for the design. In fact if you don't specify the -raw argument, then the result directory name is named based on whatever the input file was called. So that's unique. Then there's the logFile which is an index of all the results - so you a waveform tool (such as ViVA) can know what the various results databases produced by the simulator were for the specific run.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    This is a consequence of spectre supporting multiple named analyses of the same type. Each can have their own separate result database.

    So for example if my netlist looks like this:

    //

    R1 (n1 n2) resistor r=1k
    C1 (n2 0) capacitor c=1p
    V1 (n1 0) vsource type=pulse val0=0 val1=2 rise=1n width=10n period=20n

    mytran tran stop=1u
    yourtran tran stop=2u

    And I run with -f fsdb (the netlist above is in spectre syntax - so you can see I have two differently named transient analyses), I get:

    UNIX> ls myresults.raw/
    logFile mytran.tran.fsdb yourtran.tran.fsdb

    The filename has the name of the analysis instance, the type of analysis (because there could be other types) and the format as part of the name. You can't change the name of the file to match the design unless the instance name of the analysis matches the design name.

    The reason for this is that each result directory is intended to be unique for the design. In fact if you don't specify the -raw argument, then the result directory name is named based on whatever the input file was called. So that's unique. Then there's the logFile which is an index of all the results - so you a waveform tool (such as ViVA) can know what the various results databases produced by the simulator were for the specific run.

    Regards,

    Andrew.

    • 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