OpenAccess Data Translators
From oacwiki
The best way to get data into OpenAccess depends on what form your data is in today, and what you plan to do with it once it is in OpenAccess. Translators are available for Verilog, LEF, DEF, GDSII and SPEF. If you don't plan to use any more information than was in the file format you translate from, you're good to go.
If you need more integrated information, then you need to be more careful about which translators you use and in which order. And if you want information that simply isn't present in the formats you have available, you may need to run some applications to derive the information you need. For example, GDSII does not represent connectivity information. Although many shapes in GDSII have signal names associated with them, you would need to run an application such as an extraction engine to create oaNets from that information.
Many people have both Verilog and DEF available to them. Between the two formats, you can build up a good picture of both the logical and physical connectivity (the module domain and the block domain).
A good source of information on how to use the translators to do this can be found on-line in the Programmer's Guide article on translator flows, or in your locally installed OpenAccess documentation at doc/oa/html/guide/translationflow.html.
Formats
The pages in the list below address the usage of each format:
