Stats

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

Format for montecarlo sweep in a *.scs file included with ADE Assembler

greywanderer

mctrans montecarlo numruns=10 variations=mismatch seed=1 json=yes savemismatchparams=yes \\ <-----UNEXPECTED END OF LINE
                              mismatchscalarfile="*/*/mis_sc_file.txt" \\
                              mismatchparamfile="*/*/mis_par_file.txt" \\
                              dumpseed=yes savefamilyplots=yes {
                                       tran tran stop=5u save=selected
                                       }                                                                                                                       <---------- UNEXPECTED END OF BLOCK STATEMENT

Is the above a valid way to include the montecarlo sweep. I see and "unexpected end of line" error on the first line and an "unexpected end of block statement" error on the last line.

Thanks much!

  • Presumably the double backslashes are because you're using a stimulus file? I wonder why you keep doing that - it certainly works OK if you use this as a normal included file (with single backslashes): 

    mctrans montecarlo numruns=10 variations=mismatch seed=1 json=yes savemismatchparams=yes \
                                  mismatchscalarfile="*/*/mis_sc_file.txt" \
                                  mismatchparamfile="*/*/mis_par_file.txt" \
                                  dumpseed=yes savefamilyplots=yes {
                                           tran tran stop=5u save=selected
                                           }        

    Are the double backslashes ending up in the final file that Spectre is reading? If so, I get the errors like you do. 

  • in reply to Andrew Beckett

    I just found out my error. I was including it as a definition file and using double backslashes. Sorry about that. Should have resolved it myself.

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.