Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 9827
  • 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

getting the timestamp of last modify of a cellView instance

yochaym22

Hello, 

im creating pcell using the pcDefinePcell and retrieving the cellview with pcCellView. i want to to get the timestamp of the last pcell instance modify.

i have tried using the layout window and geGetSelectedSet() and the then in the CIW by using cv~>fileTimeStamp and this seems to be the correct value of the last modify done in the cellview.
when im working with the pcCellView and trying to access the pcCellView~>fileTimeStamp im getting a nil value, i looked at the pcCellView params and found param called cell and in it i have found lastModify param. 

i couldn't find documention of this param except it mentioned in the CellView  Attributes as "Cell expressed as a database object." 

i want to get the last modify by the pcCellView. meaning i need a timestamp of the creation if its just a creation of new pcell instance or changing the parameters of existing instance 

Thanks 

Yohai Mizrahi. 

Parents
  • Andrew Beckett

    Hi Yohai,

    The pcCellView variable within PCell code is set to the subMaster (i.e. the variant being generated for a unique set of PCell parameters). As such, this doesn't exist on disk, so the fileTimeStamp doesn't make any sense - so it returns nil. You can find the last time the superMaster (the cellView which contains the PCell code and manages all the variants) by doing pcCellView~>superMaster~>fileTimeStamp. The info you were retrieving with the method you used was: pcCellView~>cell~>lastModify - this is looking at the dd object for the cell directory in the library - this is the date that the cell directory last changed, which is undoubtedly not what you want. This lastModify attribute is documented in the "Attributes of Data Management Objects" section of the "Design Management" chapter of the "Virtuoso Design Environment SKILL Reference" manual (you can find this by using the Help menu in any Virtuoso window, and in the search box at the top enter "lastModify").

    I didn't entirely understand your last sentence "meaning i need a timestamp of the creation if its just a creation of new pcell instance or changing the parameters of existing instance". You can't find the time the parameters on the instance were changed (it's not recorded anywhere) - all you can do is find the time stamp when the PCell itself changed (which I've given you how to do above via the superMaster) - but perhaps that's what you meant?

    Regards,

    Andrew

Reply
  • Andrew Beckett

    Hi Yohai,

    The pcCellView variable within PCell code is set to the subMaster (i.e. the variant being generated for a unique set of PCell parameters). As such, this doesn't exist on disk, so the fileTimeStamp doesn't make any sense - so it returns nil. You can find the last time the superMaster (the cellView which contains the PCell code and manages all the variants) by doing pcCellView~>superMaster~>fileTimeStamp. The info you were retrieving with the method you used was: pcCellView~>cell~>lastModify - this is looking at the dd object for the cell directory in the library - this is the date that the cell directory last changed, which is undoubtedly not what you want. This lastModify attribute is documented in the "Attributes of Data Management Objects" section of the "Design Management" chapter of the "Virtuoso Design Environment SKILL Reference" manual (you can find this by using the Help menu in any Virtuoso window, and in the search box at the top enter "lastModify").

    I didn't entirely understand your last sentence "meaning i need a timestamp of the creation if its just a creation of new pcell instance or changing the parameters of existing instance". You can't find the time the parameters on the instance were changed (it's not recorded anywhere) - all you can do is find the time stamp when the PCell itself changed (which I've given you how to do above via the superMaster) - but perhaps that's what you meant?

    Regards,

    Andrew

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.