• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. saveDerived in Assura doesn't work

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 1322
  • 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

saveDerived in Assura doesn't work

janko
janko over 16 years ago

Hi,

 I am trying to generate fill structures using Assura DRC and therefore want to output the derived layer to somewhere. I am trying to use the saveDerived rule to save it to the extracted view:

  saveDerived( m2fill ("m2fill" "drawing" ) ext_view ) 

 But nothing happens. I tried copyGraphics(), and that one works:

  copyGraphics( ( "met2" "drawing" ) all )

However, it can only be used on original graphics layers, not derived ones.

What's wrong? Do I have to set certain switches, is there a typo anywhere or what else? The saveDerived rule doesn't even appear in the log (all the other rules do).

 I am using 5.1.41.

Any help is greatly welcome.

Kind regards,

  Ingo.

  • Cancel
  • AmitBiswas
    AmitBiswas over 16 years ago
    Ingo, In Assura DRC saveDerived doesn't work. If you want to use saveDerived command then you should run from verify->DRC but here it will derive in that particular layout itself. Or if you want to use Assura to save in other layout you have to use RSF (RUN SPECIFIC FILE) where you can use "outfile" command to dump the extracted layers. Here you have to give new output library name. Hope it will help you. Regards, Amit
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • janko
    janko over 16 years ago

    AmitBiswas said:
    Ingo, In Assura DRC saveDerived doesn't work.

    This I was trying to find out. My personal experience says you're right, however the documentation (Assura Physical Verification Command Reference, Product Version 3.1.7) states:

    "You can specify an extracted view output by using the avRCX command in your RSF. An extracted view that contains polygonal data can be created in the DRC flow. In the LVS and RCX flows, the extracted view can contain both polygonal data and netlist data."

    But how?  

    AmitBiswas said:
    If you want to use saveDerived command then you should run from verify->DRC but here it will derive in that particular layout itself.

    This is what I resorted to doing. Using Diva works fine - however, I wanted to use the more powerful fill generation functions that Assura offers. Something is clearly strange here - they implement a bucketfull of powerful fill generation functions and then (deliberately?) left out any way to save the results?

    AmitBiswas said:
    Or if you want to use Assura to save in other layout you have to use RSF (RUN SPECIFIC FILE) where you can use "outfile" command to dump the extracted layers. Here you have to give new output library name. Hope it will help you. Regards, Amit

    I thought that the Assura Run DRC form took care of creating that RSF file for me. At least it lets me specify if I want an extracted view created. And it does that, as the successful "copyGraphics" shows. It just ignores the saveDerived directive, as well as outFile. I haven't tried outFile in an explicit RSF yet, though.

    Thanks for your info, and for taking the time to answer. However, I still hope there's somebody out there who can make saveDerived work somehow, though. I hope you don't mind. 8-)

      

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information