Stats

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

Parents

  • I wonder if this is because your directory hierarchy has the extra "org" directory in it? Normally the directory structure would be:

    /MydfII/simulation/sim_osc2_gmbias/spectre/schematic - containing netlist and psf dirs

    and then the new numbered dir would be:

    /MydfII/simulation/sim_osc2_gmbias/spectre/32 - containing netlist and psf dirs

    i.e. it copies the "view" directory.

    It may be that the non-ADE-like directory structure is confusing things?

    Regards,

    Andrew.

Reply

  • I wonder if this is because your directory hierarchy has the extra "org" directory in it? Normally the directory structure would be:

    /MydfII/simulation/sim_osc2_gmbias/spectre/schematic - containing netlist and psf dirs

    and then the new numbered dir would be:

    /MydfII/simulation/sim_osc2_gmbias/spectre/32 - containing netlist and psf dirs

    i.e. it copies the "view" directory.

    It may be that the non-ADE-like directory structure is confusing things?

    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.