Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 12920
  • 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

Force simulation to overwrite previous .fc files

david73

Hi

I have a testbench in which i want to recycle the .fc file of one simulation to be a node set for the next simulation.

I have a set up cross corner so that the file is always written to a deterministic location, and the nodeset is read from the same location

The problem is, that if there is a file of the same name, the simulation won't wrte a new updated .fc file there.

I see that the file is "touched" but when i open it, I see that it is old

How can i tell Spectre/ADE to overwrite the old file if it finds one of the same name?

Parents
  • Andrew Beckett

    David,

    That's not true. Spectre will quite happily overwrite a file with the same name as a writefinal file from the analyses. Perhaps you're seeing an NFS/filesystem issue where you're seeing a stale cache - which is a problem with the OS/filer setup, and not the simulator. I have never seen any issue with spectre not writing to an existing file in this way, and I'd be absolutely amazed if that was ever the case in any version (I just checked myself to make double sure, and it definitely doesn't behave this way in a few experiments).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    David,

    That's not true. Spectre will quite happily overwrite a file with the same name as a writefinal file from the analyses. Perhaps you're seeing an NFS/filesystem issue where you're seeing a stale cache - which is a problem with the OS/filer setup, and not the simulator. I have never seen any issue with spectre not writing to an existing file in this way, and I'd be absolutely amazed if that was ever the case in any version (I just checked myself to make double sure, and it definitely doesn't behave this way in a few experiments).

    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.