Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 18032
  • 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

editing input.scs not working

Rob Gregoire

Hi folks,

I'm running 6.1.5 and I ocasionally need to edit the simulation netlist (for example, to comment out a parasitic capacitance to debug). In the "old days" you would edit the input.scs and then hit simulation ->run and it would run without generating a new netlist. However, with this version it doesn't always use the input.scs - it seems to have one in memory that it uses. That is, if I go to simulation->netlist->display netlist I get the input.scs file that I modified, but the simulation uses the old one. (Editing the file "netlist" doesn't seem to help either.)

Occasionally I can get it to use the modified one, but I'm not sure exacly what I did to get it to do that. It is difficult to debug when you don't know what netlist is being used! So, what netlist is being used? How do I get it to use one that I've modified? 

 

Thanks, this problem is quite frustrating.

Rob

 

 

Parents

  • Note that this (using runSimulation) won't actually work unless you take into account what I said earlier. If in "interactive" mode (which tito80 wasn't, because aps was being used, the script says:

    # runSimulation scripts generated for spectre interactive are not intended to be used for command line.
    spectre  input.scs +escchars +log ../psf/spectre.out +inter=mpsc +mpssession=spectre0_5417_1  -format psfxl -raw ../psf
    -I/home/username/demos/OCEAN/Models +lqtimeout 900 -maxw 5 -maxn 5

    You'd find that if you ran this, it would hang - because it is waiting to be controlled by ADE. You'd have to either generate the runSimulation script when in "batch" mode, or edit out the  +inter=mpsc +mpssession=spectre0_5417_1 part.

    So it wouldn't have worked for Rob unless the advice I gave had been taken into account.

    Regards,

    Andrew.

Reply

  • Note that this (using runSimulation) won't actually work unless you take into account what I said earlier. If in "interactive" mode (which tito80 wasn't, because aps was being used, the script says:

    # runSimulation scripts generated for spectre interactive are not intended to be used for command line.
    spectre  input.scs +escchars +log ../psf/spectre.out +inter=mpsc +mpssession=spectre0_5417_1  -format psfxl -raw ../psf
    -I/home/username/demos/OCEAN/Models +lqtimeout 900 -maxw 5 -maxn 5

    You'd find that if you ran this, it would hang - because it is waiting to be controlled by ADE. You'd have to either generate the runSimulation script when in "batch" mode, or edit out the  +inter=mpsc +mpssession=spectre0_5417_1 part.

    So it wouldn't have worked for Rob unless the advice I gave had been taken into account.

    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.