Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 16383
  • 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

Save variables to a file and load them later

zmleitao

Is there an easy way in SKILL to save variables to a file so as to be able to later loading them from that same file.

I am interested in saving tables and lists, for instance.

Parents
  • Andrew Beckett

    Actually tables do have a means of writing them to a file - there's writeTable() and readTable(). Of course the downside is that you can only read/write a single table to a file, which may not be what you want. 

    Lists can easily be written out, using pprint(), or fprintf(port "%L" ...) and then read back in with lineread. You might want to use sstatus(fullPrecision t) to ensure that floats inside the lists keep more precision.

    There is a means of serializing floats, using saveFloat() and restoreFloat(), but SKILL doesn't have a generic seralization capability (like pickle in python). Some things are inherently dynamic and would be hard to serialize. Contexts are sort of that capability though, and with loadTopContextForms() you have a better way of serializing code that needs to be re-invoked at context usage time.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Actually tables do have a means of writing them to a file - there's writeTable() and readTable(). Of course the downside is that you can only read/write a single table to a file, which may not be what you want. 

    Lists can easily be written out, using pprint(), or fprintf(port "%L" ...) and then read back in with lineread. You might want to use sstatus(fullPrecision t) to ensure that floats inside the lists keep more precision.

    There is a means of serializing floats, using saveFloat() and restoreFloat(), but SKILL doesn't have a generic seralization capability (like pickle in python). Some things are inherently dynamic and would be hard to serialize. Contexts are sort of that capability though, and with loadTopContextForms() you have a better way of serializing code that needs to be re-invoked at context usage time.

    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.