Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 14865
  • 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

How to automatically run a user defined procedure after creating extracted view?

fatcat1206

Hi All

I have written a piece of code, to create a table which holds the design version (controlled by a third party tool) of every sub-blocks through design hierarchy.

One of the user case is to add such table from a layout view into the property of the corresponding extracted view. Then during the iteration of modifying the layout and re-create extracted view, it's always possible to trace the changes for each version of the extracted view.

Currently, I want to make this action automatically done, when creating the extracted view by using "Run PVS - QUANTUS QRC..." in the GUI.

Does anyone knows:

  • How to trigger a procedure, after creating the extracted view automatically?
  • Hot to collect the input design info from the "Run PVS - QUANTUS QRC..." setup?
  • Hot to collect the output view from the "Run PVS - QUANTUS QRC..." setup?

Best Regards

Yi

Parents
  • 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 <cellName>.env file in the folder mentioned in "-directory_name" line.
    The corresponding discussion with Cadence support is in the Case 46037631

    Best Regards

    Yi
Reply
  • 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 <cellName>.env file in the folder mentioned in "-directory_name" line.
    The corresponding discussion with Cadence support is in the Case 46037631

    Best Regards

    Yi
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.