Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 17456
  • 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

spectre.out file in psf directory

nicola91it

Hi,

I have a script (external to Cadence) that needs to run Spectre multiple times, and manipulates the resulting files at every run. For my understanding, the following code can launch spectre from the terminal:

spectre MY_SPECTRE_NETLIST.scs

This will generate the output files in the folder  ..../psf 

Now,  instead of directly providing the netlist, because of the script I have to pass it like the following:

spectre {0}

Where {0} is the way I have to use to pass MY_SPECTRE_NETLIST.scs, which is named differently at every run by the script. Then, according to the script, I also have to provide an information about the output files, which Will be also re-named.  For example,

spectre {0} -r {1}

Will also create a differently named folder where it will store the output files at every run, according to whatever {1} does. So, for example, if the script uses a name MY_OUTi, I Will have MY_OUT1/, MY_OUT2/, and so on.

The problem here is that {1} expects a file (for my understanding it is spectre.out file), but in the documentation I can only find the commands to change the psf directory, and nothing about the spectre.out file. How can I do that?

If I can make it more clear, I report here a working example using eldo:

eldo -i {0} -o {1}

Where {0} is taking the eldo netlist (.cir) and {1} is taking the eldo output file (.chi).

I Hope this is clear enough (unfortunately I cannot share any insights about the script). Thanks in advance!

Nicola

Parents
  • Andrew Beckett

    Hi Nicola,

    Rather than specifying -r or -raw, use -outdir:

    spectre {0} -outdir {1}

    (not sure where this {0} and {1} are coming from or what scripting language you're using is). Anyway, with -outdir, the default log file (which will be the name of the input file with a .log suffix) any saved PSF data, any other files that are written, will be written into the specified output directory.

    Regards,

    Andrew.

  • nicola91it
    in reply to Andrew Beckett

    HI Andrew,

    Thanks for the reply.  Unfortunately I already looked at outdir but it doesn't do the job. The script needs an output file and {i} simply uses names handled by the script to rename these output files (so I cannot specify a specific name myself).

    Anyway, I found out that the syntax which is supported is:

    Spectre -f nutascii -c 132 -r {1} {0}

    Where {1} is the output and {0} the input files respectively. 

    Kind regards,

    Nicola

Reply
  • nicola91it
    in reply to Andrew Beckett

    HI Andrew,

    Thanks for the reply.  Unfortunately I already looked at outdir but it doesn't do the job. The script needs an output file and {i} simply uses names handled by the script to rename these output files (so I cannot specify a specific name myself).

    Anyway, I found out that the syntax which is supported is:

    Spectre -f nutascii -c 132 -r {1} {0}

    Where {1} is the output and {0} the input files respectively. 

    Kind regards,

    Nicola

Children
  • Andrew Beckett
    in reply to nicola91it

    Nicola,

    If you're specifically wanting to look for the log file, then you could use the +log fileName or =log fileName option to write to a specific file name. Normally the log file name is derived from the input file name, but that can be overridden to anything you want.

    Andrew.

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.