checkAndSave marker creation in specific location

[Nicolas]

Cadence has a few shortcomings in their checkAndSave checks, so we
implement our own. One drawback is that we can only insert a warning/
error marker in a position "determined by the software" using the
following function:

geCreateMarker(
d_dbobjectId
t_severity
t_owner
t_reason
t_displayText
)
=> d_shapeId / nil

Creates a box-shaped marker whose size and position are determined by
the software.

-------------------

Does anyone know the (undocumented?) function to create markers at a
designated location with a specific size?

thanks!

 

[fogh]

Nicolas wrote:

Cadence has a few shortcomings in their checkAndSave checks, so we
implement our own. One drawback is that we can only insert a warning/
error marker in a position "determined by the software" using the
following function:

geCreateMarker(
d_dbobjectId
t_severity
t_owner
t_reason
t_displayText
)
=> d_shapeId / nil

Creates a box-shaped marker whose size and position are determined by
the software.

-------------------

Does anyone know the (undocumented?) function to create markers at a
designated location with a specific size?

thanks!
geCreateMarkerByPoints and geCreateMarkerByBBox may help, but you

would be safer by going low-level: simply create your geometry yourself,
using the "db" functions, for example on the layer-purpose-pair
("marker" "warning") , and then just add (still with a "db" function)
the string properties markerOwner and markerReason to that geometry. I
don t know if fancy marker shapes would be supported by error browsers.

Care to share your improvements to check and save ?

 

[Nicolas]

On Jul 31, 2:01 pm, fogh <a...@xs4all.nl> wrote:

Nicolas wrote:
Cadence has a few shortcomings in their checkAndSave checks, so we
implement our own. One drawback is that we can only insert a warning/
error marker in a position "determined by the software" using the
following function:

geCreateMarker(
d_dbobjectId
t_severity
t_owner
t_reason
t_displayText
)
=> d_shapeId / nil

Creates a box-shaped marker whose size and position are determined by
the software.

-------------------

Does anyone know the (undocumented?) function to create markers at a
designated location with a specific size?

thanks!

geCreateMarkerByPoints and geCreateMarkerByBBox may help, but you
would be safer by going low-level: simply create your geometry yourself,
using the "db" functions, for example on the layer-purpose-pair
("marker" "warning") , and then just add (still with a "db" function)
the string properties markerOwner and markerReason to that geometry. I
don t know if fancy marker shapes would be supported by error browsers.

Care to share your improvements to check and save ?

We found holes in the reserved keywords checking (for AMS mainly). In
other words, Cadence is not catching all VHDL/verilog reserved words,
according to the IEEE syntax standards. We've informed Cadence but
its taking the big fish years to add the missing coverage.

Examples of reserved words getting flagged:
- in
- out
Examples of some that are not getting flagged:
- cell
- ceil
- ddt
- wreal

(easiest way to confirm is to create a pin with one of those names and
run a CheckAndSave (with AMS checks turned on).
So far we found 36 un-covered words ...

We hit some snags in AMS sims due to some of these .. don't remember
which one anymore ...

Let me know if you wish to see the full list ...

Nicolas

 

[Nicolas]

Fogh:

what is the t_type argument of geCreateMarkerByPoints() ? is it to
specify the kind of shape to create ? i.e. "rect" ?

 

[fogh]

Nicolas wrote:

Fogh:

what is the t_type argument of geCreateMarkerByPoints() ? is it to
specify the kind of shape to create ? i.e. "rect" ?

Nicolas,
that is the purpose , either "warning" or "error"
I imagine that you can leave empty strings for owner and displaytext.

 

[Andrew Beckett]

fogh wrote, on 08/01/08 12:57:

Nicolas wrote:
Fogh:

what is the t_type argument of geCreateMarkerByPoints() ? is it to
specify the kind of shape to create ? i.e. "rect" ?

Nicolas,
that is the purpose , either "warning" or "error"
I imagine that you can leave empty strings for owner and displaytext.

In OA, you also have dbCreateMarker() - markers are separate objects in OpenAccess.

Regards,

Andrew.