invoke pcell callback - simple case of abInvokeCdf... functions?

Sorry, here's the full question text:


We would like to invoke a layout pcell callback from SKILL code.

After reading through the forum post on design migration and abInvokeCdfCallbacks (community.cadence.com/.../1340918) and the help case 'How to call CDF callbacks procedurally from SKILL?' (support.cadence.com/.../ArticleAttachmentPortal;pageName=ArticleContent&sq=0050V000006PHLGQA4_201772013217119 


I have a couple of questions:

1) are those two related? Did CCSinvokeCdfCallbacks originate from abInvokeCdfCallbacks?

2) is the full complexity of the lookalike CDF needed if I'm just operating on one instance of once layout pcell, and not on a cellview or library?

3) if you invoke one callback, will it automatically cascade to invoke the child callbacks? If we call a callback for a, which changes b, will the callback for b get called automatically or do we need to separately invoke the

callback for b? Seems like the answer is 'no' for safety reasons, i.e. to prevent unintentional dependency loops?

3) is there any hope of this functionality becoming a supported part of the normal SKILL API that ships with Virtuoso? It seems pretty dang handy and universal, and it seems like a whole lot of folks would need something

like this.


Our particular use case is something like this:


We place a pcell of a certain capacitor type from code. We specify its capacitance. Since the area capacitance coefficient is a constant for this device type, and we assume a square capacitor at this point, W and L are

(basically) just a function of C.

The pcell has a parameter 'force square' which is a boolean, and if t

(by default), then w and l will be the same (or very close), and a non-editable cdf parameter showing the actual realized capacitance based on w and l, and another param showing how close that is to the intended

capacitance, will get automatically updated when the form is open.


So - when the form is open and we change C and 'force square' is on, that one change results in changes to W, L, 'C(actual)' and 'error'.


When we place the capacitor using code, and specify C, none of W, L, C(actual), or error are updated. This is no surprise since the callbacks are not called - just wanted to be clear about what we are seeing.


So really we want to call the callback for the intended capacitance field, and if there is no automatic cascading, also call the callbacks for W, L, and C(Actual).



Thanks

Sorry, here's the full question text:


We would like to invoke a layout pcell callback from SKILL code.

After reading through the forum post on design migration and abInvokeCdfCallbacks (community.cadence.com/.../1340918) and the help case 'How to call CDF callbacks procedurally from SKILL?' (support.cadence.com/.../ArticleAttachmentPortal;pageName=ArticleContent&sq=0050V000006PHLGQA4_201772013217119 


I have a couple of questions:

1) are those two related? Did CCSinvokeCdfCallbacks originate from abInvokeCdfCallbacks?

2) is the full complexity of the lookalike CDF needed if I'm just operating on one instance of once layout pcell, and not on a cellview or library?

3) if you invoke one callback, will it automatically cascade to invoke the child callbacks? If we call a callback for a, which changes b, will the callback for b get called automatically or do we need to separately invoke the

callback for b? Seems like the answer is 'no' for safety reasons, i.e. to prevent unintentional dependency loops?

3) is there any hope of this functionality becoming a supported part of the normal SKILL API that ships with Virtuoso? It seems pretty dang handy and universal, and it seems like a whole lot of folks would need something

like this.


Our particular use case is something like this:


We place a pcell of a certain capacitor type from code. We specify its capacitance. Since the area capacitance coefficient is a constant for this device type, and we assume a square capacitor at this point, W and L are

(basically) just a function of C.

The pcell has a parameter 'force square' which is a boolean, and if t

(by default), then w and l will be the same (or very close), and a non-editable cdf parameter showing the actual realized capacitance based on w and l, and another param showing how close that is to the intended

capacitance, will get automatically updated when the form is open.


So - when the form is open and we change C and 'force square' is on, that one change results in changes to W, L, 'C(actual)' and 'error'.


When we place the capacitor using code, and specify C, none of W, L, C(actual), or error are updated. This is no surprise since the callbacks are not called - just wanted to be clear about what we are seeing.


So really we want to call the callback for the intended capacitance field, and if there is no automatic cascading, also call the callbacks for W, L, and C(Actual).



Thanks