Stats

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

Stop XStream from custom skill procedure

Adrian Nistor

Hello,

I know that XStream is passing each cell to some functions like poParamCellNameMap() or poCellNameMap() in order to change the name of the cells inside the exported gds file; My problem is that I would like to stop the process if I detect one PCell which has some problems.

Is there any possibility to make this ?

 

(More details about my problem: I want to detect PCells which can not be created (functions missing, errors, etc) in the layout; The layouter can load locally made pcell scripts, he can have a pcell layout in he's layour, but when he will export to stream/gds, that locally created pcell will be skipped (for some reasons we maintain "Stream out from virtual memory" disabled and we do not want to enable it). I would like to detect cases like this during the process of exporting and, using a skill script to analyze, to stop te exporting process)

 (I'm using Virtuoso 6.1.4)

 

 

Thank you,

Best Regards,

Adrian

Parents

  • You could print your useful information and then add return(nil) to cause the failure. Unfortunately, I don't know how to control the size of the pcellEvalFailed message. Maybe one of the Cadence insiders knows a trick for that so you can avoid oversized instances of your failed pcells.

    Derek

Reply

  • You could print your useful information and then add return(nil) to cause the failure. Unfortunately, I don't know how to control the size of the pcellEvalFailed message. Maybe one of the Cadence insiders knows a trick for that so you can avoid oversized instances of your failed pcells.

    Derek

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.