leHiTree in Skill

Hi,

Does anyone know of a way in Skill to get Layout tree file with a
cellview ID as argument?

leHiTree & leiHiTreeCB() are not what I am looking for since they are
interactive. I've got code for schematic tree files, but not layout
tree files.

thanks
Nicolas

 

Ah,

I just found some good cadence AE-ware that did the job. A set of
functions by Andrew Beckett with main function abSchTree() worked like
a charm -- just had to pass "layout" as viewList and it worked fine.
The code had to be touched up to handle broken links (missing masters)
and infinite loops due to instantiation of the same cell(s). The
order of traversal is slightly different, so the order of branches of
the tree do not appear in the same order as the leHiTree() (shift-t)
function. Nevertheless the data is just as complete and valid.

cheers,
Nicolas

 

Note, you might want to get a more recent version of the code in sourcelink
solution 11300048 - this also handles config views now.

Regards,

Andrew.

 

leHiTree & leiHiTreeCB() are not what I am looking for

I realize you are not planning to use these functions but whenever a
private SKILL function (leiHiTreeCB) is thrown out there to the
public, the standard warning applies, lest we return to the bad ole'
days when SKILL was harder to migrate from release to release.

<soapbox>
As always, please bear in mind that private functions are undocumented
and unsupported, subject to change or deletion at any time. Most
private functions are designed for specific circumstances and
therefore do little to no checks beyond the bounds of the intent for
which they were written. Most, if not all, release-to-release SKILL
changes & deletions are to private functions.

A simple five-minute CIW: Tools -> SKILL -> Survey will identify all
the private functions in use (and all changed or deleted functions,
what the changes are, and how to recover from them). Customers who run
these SKILL Surveys periodically and who replace private functions
with their public equivalents have been shown to have few to no
migration problems, release to release - even when many hundreds of
thousands of lines of SKILL code are involved.
</soapbox>

Whew! There. I said it.