Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 3398
  • 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

Re: evaluating of variables in netlist created by maeCreateNetlistForCorner

slim15

Hi,

When using maeCreateNetlistForCorner to create netlist, I noticed that the input.scs created by the command line has difference compare to the ones created by GUI in Explorer/Maestro. For example, via GUI  the top part of the input.scs from the two methods are shown below

// GUI 

simulator lang=spectre

global 0

parameters VDD=900m freq1=1.0G freq2=1.1G SIM_END=10.0/(freq2-freq1)

// command line

simulator lang=spectre

global 0

parameters VDD=0.9 freq1=1.0000000000000000e+9 1.1000000000000000e+9 freq2=1.10000e+9 SIM_END="10.0/(freq2-freq1)" 

Is there a flag that should be set before executing the maeCreateNetlistForCorner command to make the input.scs generated by the command line to be the same as that generated by GUI?

Regards

slim

  • Which IC sub-version are you using? Is the netlist from the "GUI" created by virtue of running the simulation, or are you doing it from the Run Preview tab (otherwise how are you creating the netlist for a specific corner)? I assume the issue is not really the numbers but the SIM_END being a string (that looks wrong, and looks like a bug to me). I don't see otherwise why it would matter whether 1.100000e+9 is used instead of 1.1G.

    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.