Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 14249
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with dbLayerOr

ToMWUT

I've got an algorithm, which behaves a little strange since I've decided to use my function to perform OR operation on all objects which belongs to one list. The function I'm talking about looks like this:

procedure(or_shapes(cv shape_list)

prog((ret_shapes)

if((length(shape_list)<2) then

ts_ui_warning("ts_or_one_list_ver_2_shape_points" "Entry list smaller than 2 elements!")

return(shape_list)

);if

ret_shapes=dbLayerOr(cv lppA shape_list)

return(ret_shapes)

);prog

);procedure

The lppA is a layer purpose pair which is a defined global. I'm also using an empty CV to perform the operation. From Cadence manual I figured out that this function should perform OR operations on all shapes given on shape_list. What I mean is operation which for overlapping regions of shapes in shape_list returns this overlapping region only once.

And now the usage and the limitations. My algorithm in pseudo code looks something like this:

 

in_area=Area(seed)

seed=Oversize(seed, k)

after_oversize=Area(seed)

seed=or_shapes(seed)

out_area=Area(seed)

And now some background. Area(x) returns valid area of she list, which I've checked. In seed at the beginning there are some shapes which do not overlap (I've executed the or_shapes procedure). Oversize(x,k) oversizes all shapes in x by the factor k. And the problem is that the out_area<in_area (after_oversize>in_area), while it shouldn't be. In worst case the out_area should be equal to in_area. Maybe the dbLayerOr function has some limitations, or maybe I'm doing something else wrong. Any suggestions would be much appreciated.

  • I'm not aware of any problems with dbLayerOr() - I'd be surprised. Most likely is something wrong with your Area code - I'd have thought it would be fairly obvious by looking at the layout at each step.

    Perhaps you can contact me directly and then send me the code and data which shows the problem, and I'll try to take a quick look?

    Best Regards,

    Andrew.

  • Thanks Andrew,

    I found the solution to my problem. While using leSizeShape procedure it turned up that, while oversizing it is possible that the procedure returns more than one shape. In my algorithm I was prepared for just one shape and other shapes weren't taken into account in my algorithm. That's the reason why the area was smaller. By the way I'm still quite surprised that while oversizing one shape it is possible for procedures to return shapes list (more then one shape in it). How is it possible?

    ToM

  • Hi ToM,

    If the resulting shape has too many vertices (more than 4000 if I remember rightly) then it will be split into multiple shapes. There's a maximum number of allowed vertices in a polygon in the database, so it has to do this.

    That's the most likely explanation. I'm assuming shapes when oversized collide with other oversized shapes, and that could result in a shape with lots of vertices?

    Regards,

    Andrew.

  • Hi Andrew, Does dbLayerOr function support hierarchy? If not, how do I trace layer hierarchically without using diva? Thanks!! Bonnie

  • Hi Bonnie,

    First, please don't append to the end of an old thread, 7 years old in this case!

    Second please take a look at Solution 11237840 - the function CCShierLayerOps() in the solution performs layer operations through the hierarchy.

    I hope this helps!

    Lawrence.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.