In the course of performing design work in Encounter, it frequently becomes desireable to create a self-contained testcase that can be shared with colleagues at other sites, or with Cadence to aid in troubleshooting tool issues. By self-contained, I mean the design data (netlist, floorplan, placement, routing, timing constraint files, etc) and all of the supporting collateral (.libs, LEFs, extraction tech files, etc) within a sub-directory that can be tarred up and uploaded to an ftp site such that someone else can download the design and see the design just as you're seeing it. Because this data is often drawn from various shared locations on the network, symbolic links are used, and pointers often make use of shell/TCL variables, creating a self-contained testcase is frequently quite a bit more complicated than it appears at first glance. But fear not- a new command has been introduced that automates this for us.
In the Encounter Digital Implementation System version 8.1.USR2, a new public command was introduced that automates the testcase creation. It is called: "saveTestcase"
Here's how it works...
Usage: saveTestcase [-name <testcaseName>] [-dir <directoryName>] [-rc] [-merge] [-overwrite] [-gzip]
Enter "man saveTestcase" at the tool prompt in 8.1.USR2 for extended help -or- see the complete documentation on Sourcelink here.
Additional nice features:
Not using 8.1.USR2 yet?
Question of the Day: What are some of the scenarios where self-contained testcase creation is useful to you?
Thanks for the kind words! I'll pass your comments along to our developers.
Bob, this would be industry's 1st testcase submission system, congratulations. :)
Great post, Bob. I just sent the link to this post out to my entire group. We can finally get rid of our "frankenstein" scripts for making testcases.