Artist Calculator expressions <--> Ocean

S

Sylvio Triebel

Guest
Hello,

I'm curious if there is a functionality to transform
expressions from Calculator into Ocean functions.
I need this for a plot tool which displays results from ocean scrips
which where distributed per lsf...

e.g. VT("net") ---&gt; v("net" ?result "tran" ?resultsDir "...")

Our previous solution was to use the (undocumented) resultsdir argument to the
calculator functions:
VT("net") --&gt; VT("net" dir)

However, even if we got this solution from a Cadence Consultant... We found
some strange indetermined behavior. The plots of the same pdf data have sometimes
not the same domain as the corresponding simulation and even worse,
they change if you run just a local simulation (which does not change the psf data)

With the Ocean functions those strange effects have not been observed yet.

I could imagine two solutions:

1) there must be some initialization which makes the calculator functions really usable.

2) transforming ALL special functions from the Calculator into Ocean
But is it really just IT, VT, VDC... VN() VN2() ....
It seems to me that I have always to extend the plot tool if there are new
Calculator functions - if there is no Cadence script for that task.

I would be glad, if anybody could advice which way is better.

Regards,
Sylvio
 
There's no function to automatically translate these. There is a PCR to ask that
all the Artist data access calculator functions get transformed to use OCEAN
underneath, to make them compatible.

VT("net") becomes v("net" ?result "tran")

etc.

All these calculator functions are old Artist functions. Anything new tends to
use the OCEAN conventions (for example, if you use the ADE Results-&gt;Direct
Plot-&gt;Main Form function and then hit the Add to Outputs - you'll see it uses
OCEAN data access functions).

So the best fix for this will be when PCR 553544 gets fixed. In the meantime,you
need to do the transformation yourself.

Andrew.

On Thu, 19 Aug 2004 11:35:50 +0200, Sylvio Triebel &lt;Sylvio.Triebel@nospam.com&gt;
wrote:

Hello,

I'm curious if there is a functionality to transform
expressions from Calculator into Ocean functions.
I need this for a plot tool which displays results from ocean scrips
which where distributed per lsf...

e.g. VT("net") ---&gt; v("net" ?result "tran" ?resultsDir "...")

Our previous solution was to use the (undocumented) resultsdir argument to the
calculator functions:
VT("net") --&gt; VT("net" dir)

However, even if we got this solution from a Cadence Consultant... We found
some strange indetermined behavior. The plots of the same pdf data have sometimes
not the same domain as the corresponding simulation and even worse,
they change if you run just a local simulation (which does not change the psf data)

With the Ocean functions those strange effects have not been observed yet.

I could imagine two solutions:

1) there must be some initialization which makes the calculator functions really usable.

2) transforming ALL special functions from the Calculator into Ocean
But is it really just IT, VT, VDC... VN() VN2() ....
It seems to me that I have always to extend the plot tool if there are new
Calculator functions - if there is no Cadence script for that task.

I would be glad, if anybody could advice which way is better.

Regards,
Sylvio
Click to expand...
--
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd
 
Hello Andrew,
thanks a lot...
So I'll proceed with the transformation aproach.
Just a few functions I don't know how to transform - like
MP (needs first to find out the name of the model...) and
some special things like tables defined in the calculator.
However, those functions are probably non critical.

Sylvio.



Andrew Beckett wrote:
There's no function to automatically translate these. There is a PCR to ask that
all the Artist data access calculator functions get transformed to use OCEAN
underneath, to make them compatible.

VT("net") becomes v("net" ?result "tran")

etc.

All these calculator functions are old Artist functions. Anything new tends to
use the OCEAN conventions (for example, if you use the ADE Results-&gt;Direct
Plot-&gt;Main Form function and then hit the Add to Outputs - you'll see it uses
OCEAN data access functions).

So the best fix for this will be when PCR 553544 gets fixed. In the meantime,you
need to do the transformation yourself.

Andrew.

On Thu, 19 Aug 2004 11:35:50 +0200, Sylvio Triebel &lt;Sylvio.Triebel@nospam.com
wrote:


Hello,

I'm curious if there is a functionality to transform
expressions from Calculator into Ocean functions.
I need this for a plot tool which displays results from ocean scrips
which where distributed per lsf...

e.g. VT("net") ---&gt; v("net" ?result "tran" ?resultsDir "...")

Our previous solution was to use the (undocumented) resultsdir argument to the
calculator functions:
VT("net") --&gt; VT("net" dir)

However, even if we got this solution from a Cadence Consultant... We found
some strange indetermined behavior. The plots of the same pdf data have sometimes
not the same domain as the corresponding simulation and even worse,
they change if you run just a local simulation (which does not change the psf data)

With the Ocean functions those strange effects have not been observed yet.

I could imagine two solutions:

1) there must be some initialization which makes the calculator functions really usable.

2) transforming ALL special functions from the Calculator into Ocean
But is it really just IT, VT, VDC... VN() VN2() ....
It seems to me that I have always to extend the plot tool if there are new
Calculator functions - if there is no Cadence script for that task.

I would be glad, if anybody could advice which way is better.

Regards,
Sylvio


--
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top