• 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 SKILL
  3. Export and import GDS using SKILL in batch mode

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 16789
  • 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

Export and import GDS using SKILL in batch mode

Sherl
Sherl over 5 years ago

Hi all,

I want to export the GDS file from the library and import the GDS file into another library. Does SKILL support importing and exporting GDS files in batch mode?

Best regards,

Huy Hoang

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Huy,

    You can use xstSetField to set the parameters, and then xstOutDoTranslate to do the export. Then xstInSetField and xstInDoTranslate to do the import.

    Note that going via stream (aka GDS) is a lossy operation (you lose connectivity and various other non-physical aspects, and pCells get converted to fixed cells), so if this is just a means of copying data from one library to another, you'd be better off using the ccp.* functions to copy instead.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • SrBraj
    SrBraj over 5 years ago in reply to Andrew Beckett

    Hello Andrew

    So far I have been using the "system(strmout ……... )" skill APIs to export the GDS files. These xst* APIs are new to me but seems like very useful for my next scripts.

    It would be very useful if you could provide us a sample scripts to do stream out/in using the xst* skill APIs. 

    Thanks and Regards

    Saurabh Raj (SrB)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to SrBraj

    Hi Saurabh,

    This is mostly pretty obvious from reading the documentation, but here's a simple example of doing a stream out (and suppressing the completion dialog box):

    xstSetField("library" "opamp090")
    xstSetField("topCell" "adc_sample_hold")
    xstSetField("strmFile" "adc_sample_hold.gds")
    xstSetField("showCompletionMsgBox" "false")
    xstOutDoTranslate()

    The documentation shows you how to find out the field names. The stream in would be similar (using xstInSetField instead and xstInDoTranslate).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to SrBraj

    Hi Saurabh,

    This is mostly pretty obvious from reading the documentation, but here's a simple example of doing a stream out (and suppressing the completion dialog box):

    xstSetField("library" "opamp090")
    xstSetField("topCell" "adc_sample_hold")
    xstSetField("strmFile" "adc_sample_hold.gds")
    xstSetField("showCompletionMsgBox" "false")
    xstOutDoTranslate()

    The documentation shows you how to find out the field names. The stream in would be similar (using xstInSetField instead and xstInDoTranslate).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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