cadence? OCEANSKILLSPECTURECALCULATOR

[comp.cad.cadence]

Hi, pals

I'm trying to lean how to use OCEAN now. Upon reading the OCEAN
reference and some previous posts, I am still not so clear at some
point. Here I try to do a little summary of my confusion and thoughts.
I really appreciate that you can correct me or address any comments
there.

1. VT("/outp") is kinda Cadence Calculator styled expression and not
recommended in OCEAN. Instead, the v("/outp" ?result 'transient) is
better used there. But obviously the VT(...) expression is more
convenient, right?

2. pv is to get the value of the parameter of some component (most
likely, a mos transistor).
v("/t_net") is to get the value of some nod voltage
i("t_component") is to get the current through some component.
My question is:
i("/NM0") and pv("NM0" "id") are doing the same thing? (Here, to
get the drain current of a mos transistor.)

3. Is the expression getData("M0")~>cgd equivalent to pv("M0" "cgd")?
Is there difference between them? (Actually, I haven't found the
documentation about the caret expression ~>.)

4. Between the two expressions: getData("hier1.hier2.M0:1") and
getData("/hier1/hier2/M0/d"), which one should be favored to use in
writing OCEAN code? It seems that the OCEAN file you get by using "save
script" from ADE follows the second one. In previous posts, someone
mentioned that something like "terminal mapping" is responsible for the
conversion between the two ones.

5. It seems that the function getData(...) is more universal one, which
can access to any data (either single value or vector set). So it can
take place of the other functions like v(...), i(...), pv(...). Is that
right way to think of getData()?

6. As the subject of my post, Cadence is kinda mixture of many things.
Also, there exists a lot overlap among them. ?

Thanks a lot!

rgds

-Andy

 

[fogh]

comp.cad.cadence wrote:

Hi, pals

I'm trying to lean how to use OCEAN now. Upon reading the OCEAN
reference and some previous posts, I am still not so clear at some
point. Here I try to do a little summary of my confusion and thoughts.
I really appreciate that you can correct me or address any comments
there.

1. VT("/outp") is kinda Cadence Calculator styled expression and not
recommended in OCEAN. Instead, the v("/outp" ?result 'transient) is
better used there. But obviously the VT(...) expression is more
convenient, right?
right. but wrong. right.

2. pv is to get the value of the parameter of some component (most
likely, a mos transistor).
v("/t_net") is to get the value of some nod voltage
i("t_component") is to get the current through some component.
My question is:
i("/NM0") and pv("NM0" "id") are doing the same thing? (Here, to
get the drain current of a mos transistor.)
nope, getting the current through the pin will give a slightly different value

than the device parameter. Maybe a bigger slightly if inline subcircuit is used.

3. Is the expression getData("M0")~>cgd equivalent to pv("M0" "cgd")?
Is there difference between them? (Actually, I haven't found the
documentation about the caret expression ~>.)
dunno. sorry.

The squiggle arrow getSGq/setSGq is not really documented but it is explained
in some skill manual (maybe dfII database).
Look up the documentation for "disembodied property lists" or just the skill
user manual.

4. Between the two expressions: getData("hier1.hier2.M0:1") and
getData("/hier1/hier2/M0/d"), which one should be favored to use in
writing OCEAN code? It seems that the OCEAN file you get by using "save
script" from ADE follows the second one. In previous posts, someone
mentioned that something like "terminal mapping" is responsible for the
conversion between the two ones.
The first expression uses netlist namespace, the second uses schematic

namespace. You probably prefer the second.

5. It seems that the function getData(...) is more universal one, which
can access to any data (either single value or vector set). So it can
take place of the other functions like v(...), i(...), pv(...). Is that
right way to think of getData()?

6. As the subject of my post, Cadence is kinda mixture of many things.
Also, there exists a lot overlap among them. ?

Funny question, but I ll try an answer. Some functions will require that you
know and pass them many arguments. Some others are more specialised and require
less info from you. A house is a mixture of brick and mortar, a city is a
mixture of houses and streets. But you would probably prefer to specify the city
planning with coordinates of houses, not bricks.

 

[comp.cad.cadence]

Thanks so much! You're always there to help us out.
Frankly, I can't completely agree with you about the anwser to the last
question. But I'm not supposed to discuss that too much to divert the
topic of the original post.