Forum Replies Created
-
Posts
-
Are you passing values to PCells in dbu rather than microns or metres?
The schematic/symbol dbuPerUU is always 160 (to be compatible with Cadence so you can e.g transfer schematic via EDIF). The layout dbuPerUU is what you set a library to when you create it, usually 1000.
So if you pass values in dbu they will be incorrectly scaled if used directly. Is that the problem?
Sorry, no images attached to this msg. Please send images etc. to support @ peardrop.co.uk. Thanks.
Edit: Have you set the display stop/start to view all layers of the hierarchy?
I've put a beta copy of 4.6.32 with changes to the property list code that allow the use of the following function for all objects:
getPropList()
This returns a python list of 'prop' objects (alas the can't be called 'property' as this causes SWIG errors)
A prop object has the following functions:
setName(name) – set the prop name
name() – get the prop name
setType(type) – set the type, using the enum propType (stringType, integerType, floatType, booleanType)
type() – returns the propType
setData(value) – sets the prop value. Overloaded for the different propTypes.
data() – return a union of the value. So data().s resturns string value, data().i returns integer value, data().g returns float value, data().b returns boolean value.
setVisible(bool) – set whether the property should be visible in schematics
visible() – returns isVisibleIt's not documented as it's an internal function that doesn't have a SWIG wrapped data structure.
I'll need to make some changes to the code in order to make this visible and usable. I'll target it for 4.6.32, i.e. next release.
You can use a single layer AND like this:
poly = geomGetRawShapes("poly", "drawing")
ovlp = geomAnd(poly)
saveDerived(ovlp, "Poly shape overlap!")The function geomGetRawShapes() does not carry out a merge on the input data. The shapes need to be simple polygons i.e. not self-intersecting. But if you're using a specific layer, and expect all shapes to be rectangles, this condition should be met.
Other thing to check is if your fit% factor changed with the change to xml settings. You can find it under View->Pan/Zoom Options…
A Fit% of 90 is usually a good value.
Fit will use the cellView's dbuPerUU. But it's possible that the cellView bounding box was not updated after the change in dbu.
cv = getEditCellView()
cv.update()Should fix that.
Do you mean vias as in via objects, or just shapes on a certain layer?
You may need to send me an example then. Ideally with steps that reproduce the issue.
There are a few other things to check – make sure the dbu is what you expect, just query in the cellView with nothing selected and you should see the dbu. And you can try selecting everything (ctrl+a) and query, and step through each selected object to see what is there.
Vias have shapes on layers in database units, depending on the library units when created, and are stored by an index in a library. So I wonder if what's happening is that you have old ones mixed with new ones of different scale?
