How to stop when using dbGetTrueOverlaps ?

Hi Charley,

for the current level of hierarchy it is easy enough to find the number of shapes.  Assuming that "cv" stores the cellview database id, then length(cv~>shapes) gives the count of shapes (level 0) in this cellview.  As far as I am aware, unless you control the hierarchy depth yourself, there is no way to stop a function like dbGetOverlaps or dbGetTrueOverlaps mid-operation.  You could use the previous code suggestion as a starting place.  Then you might just call dbGetTrueOverlaps for 1 level of hierarchy, and if the number back is not too high, then progress onto level 2 etc. But this method would suffer the disadvantage of repeating work and getting progressively slower.  Another method might involve descending into the instances in a programmatic way; if you keep count as you go, you can choose to abort further processing.  Also you might have a global "stop" type flag that if set also prevents further processing - if the code encounters this setting during processing it stops.

 However, as I said, unless you control the hierarchy yourself I don't see how you might do this.

Regards,

Lawrence.

Hi Lawrence,

Even in current cellview , using dbGetTrueOverlap(cv cv~>bBox mylayer 0 nil)  it will take long time.

In my case , the cv has 13651864 shapes on mylayer.

In hierarchy , I can know how the depth for the cellview.  Even is has 5 level , the problem will be same as current cellview

if has 13651864 shapes on mylayer . What i do is to tranform the shapes to the top level.

Do you have better solution for this ?

Thank you,

Charley

At any level, it will take longer time if you really have many shapes.

Since your just using the bbox of the cellview, why dont you use

a=cv~>lpps, then filter lpps where lpps is your mylayer

then a~>shapes to get your shapes

Hi cessej ,

I will try it .

Thank you,

Charley

Hi cessej ,

After using  lpps to get and ~>shapes , it still takes long time .

Thank you,

Charley

I dont expect it would take longer time because the expected looping is on lpps list only which is smaller in number than the shapes objects.

Here's the sample for you.

cv=geGetEditCellView()

a=setof(x cv~>lpps x~>layerName=="M1" && x~>purpose=="drawing")

yourShapes=a~>shapes

Try doing:

needNCells('list 15000000)
needNCells('dbobject 15000000)

before your code. This may help in avoiding it garbage collecting too often every time it uses the pool of objects up. 13 million shapes is quite a lot, beyond the default pool size in Virtuoso.

Andrew.

 Hi Andrew,

It works. 

Thank you very much.

Charley