Stats

  • Locked Locked
  • Replies 14
  • Subscribers 126
  • Views 5783
  • 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

ocean script - input.scs copy

jugemu1234

Hi there,

 What I do not like about ocean scripting simulation is that no netlist nor model info would be stored in psf/ folder. netlist/ folder where those info are housed will be automatically overwritten by new simulation. So it is as default impossible to look back old netlist or model environment as far as I know. 

 Therefore I think it would be pretty better to have copy procedure of netlist/input.scs prior to running next simulation. But unfortunately I do not know how to just copy certain file to designated location in ocean script. 

Could you suggest me to do this?

Best regards,

  •  Hi markbe,

     Thanks for your response.

    I tried and I kind of made it. It surely added individual netlist folder by run to run.

    However, there seems constraint that when you use netlistDir() command, you have to use design() as well without filename option, isnt it? If I violate this constraint, following warning comes up and each input.scs wont be created.

    \o           You can not change the netlistDir because you specified the
    \o           design() using the filename option.  The netlistDir will
    \o           remain the same as the directory you specified with the
    \o           design() command.

     As you know, when creating "oceanScript.ocn" form ADE, it usually enables filename option, looking like

    design("<netlist filename>")

    Is there any magic to disable filename option in creating "oceanScript.ocn" form ADE? 

  • I just noticed that the netlistDir() function is not documented, but it is marked as a public function in our internal database - so I just filed a CCR to get it documented.

    There is no option to get ADE-L to netlist with the lib/cell/view form. That would be a (quite reasonable) enhancement request. I suggest if you want that, you contact Cadence Customer Support and ask for such an enhancement request (that way it can be associated with a real customer request).

    Regards,

    Andrew.

  • I'm trying to understand the usage of netlistDir(). What's difference between design() and netlistDir() ? It seems the same to me.

  • I'm simplifying thigs here but I believe it does the following: 

    design(): tells the netlister/simulator what cell / design you wish to netlist / simulate with

    netlistDir(): specifies which directory you want the netlister to send the generated netlist to.  It isn't used to communicate with the simulator.

     

     

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.