Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 17622
  • 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

spectremdl montecarlo simulations, how to fix my errors ?

samung
Hello,

I would like to launch some montecarlo simulations through spectremdl commandline interface.

I launch :
spectremdl -batch input.mdl -design input.scs -measure mc_results_file/results_file +log mc_log_file.log

I have the errors :
Error found by spectre.
    ERROR: line 11, column 2: syntax error before or at: <eof>
            unrecognised statement
    ERROR (MDL-6): Failed to parse MDL control file, `input.mdl'.

I don't know how I can fix these errors. Could you please help me ?

Thanks !!

Pedro


I have the following files :

###################################
input.mdl :

/* mdl measurement file */


alias measurement tran_meas {
    run tran
    export real test = 1000
}

run montecarlo (numruns=50, variations='mismatch, scalarfile="mc_results.dat", donominal='no) {
    run tran_meas
}


####################################
input.scs :

subckt inv A1 YN vdd vnw vpw vss
...
M5 (YN A1 vdd vnw) psvtlp w=wp*10e5 l=lp*10e5 nfing=pfolds mult=1 \
        srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1
...
M1 (saout_b saout vss vpw) nsvtlp w=wndiff l=lndiff nfing=1 mult=1 \
        srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1
include "./_graphical_stimuli.scs"
ic aout=1 aout_b=0 
simulatorOptions options reltol=1e-3 vabstol=1e-6 iabstol=1e-12 temp=70.0 \
    tnom=27 scalem=1.0 scale=1.0 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5 \
    digits=5 cols=80 pivrel=1e-3 sensfile="../psf/sens.output" \
    checklimitdest=psf 
tran tran stop=20n write="spectre.ic" writefinal="spectre.fc" annotate=status maxiters=5
finalTimeOP info what=oppoint where=rawfile
modelParameter info what=models where=rawfile
element info what=inst where=rawfile
outputParameter info what=output where=rawfile
designParamVals info what=parameters where=rawfile
primitives info what=primitives where=rawfile
subckts info what=subckts  where=rawfile
save aeni aout aout_b
saveOptions options save=allpub subcktprobelvl=2


Parents

  • I'm out of the office today (and tomorrow), but will carefully read through your various posts and give more thought out answers, but to answer this issue with the amap directory - you only need that if you use schematic names for your signals. Because your expressions are using v("/aout_b") etc - the "/" at the beginning tells it that it's a "schematic" name rather than a "netlist" name. If you omit the leading "/" it will assume it's a netlist name (so you have to use "." as the hierarchy delimiter rather than "/" too) - and then the amap dir is not needed.

    More when I have a chance to respond properly

    Regards,

    Andrew.

Reply

  • I'm out of the office today (and tomorrow), but will carefully read through your various posts and give more thought out answers, but to answer this issue with the amap directory - you only need that if you use schematic names for your signals. Because your expressions are using v("/aout_b") etc - the "/" at the beginning tells it that it's a "schematic" name rather than a "netlist" name. If you omit the leading "/" it will assume it's a netlist name (so you have to use "." as the hierarchy delimiter rather than "/" too) - and then the amap dir is not needed.

    More when I have a chance to respond properly

    Regards,

    Andrew.

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.