Hi Andrew I have tried the code the link. It has several bugs: 1. Change the index in the "for" loop. 2. The algorithm cannot parse the content in "-design_cell_name line" correctly. as the algorithm assume just one value for a key. But after parsing string with space character, the "-design_cell_name line" line would have multiple values for the key. I fixed those bugs, finished the script and test it in the IDE, it worked fine. But when I add the script into the flow of "avExtractedViewCallProc", there are some issues pops up. I receive error message in the log file of extraction, it refers to the "Undefined Function". It seems that all the functions I have used should be contained in that single file mentioned in the GUI This cannot be implemented in my case, as there is whole API library for DesignSync, and I rely on it to retrieve the version number of the design. I have submit a case in the Cadence support for this issue. The Case identification number is:46037627 Currently, Saloni suggests me to use the trigger function in PVS ( PVSPostFormTrigger() ), and then create a file in the "rundir_pvs" to store the design version, in the end, inside the "avExtractedViewCallProc" I just use some simple code to read the file and add it into a property of extracted view. This flow works, but I still have a concern. As the procedure name is fixed, how can I solve the infliction if someone else also define his "PVSPostFormTrigger". Another thing is that, the layout info is not save in the "-design_cell_name line", instead it's in the .env file in the folder mentioned in "-directory_name" line. The corresponding discussion with Cadence support is in the Case 46037631 Best Regards Yi
↧