Skew edges created in IC6.1.5

Eugene,

I tried this, and couldn't see the issue. So, either report this to customer support, or maybe you can give some precise details as to how you're creating the shapes - maybe the rodCreatePath() call you're using? Also, what's the value of DBUperUU in your cellView?

geGetEditCellView()~>DBUPerUU

Kind Regards,

Andrew.

Hi Andrew,

Thank you for the reply. The code I used to create the path is

rodCreatePath(

?layer "M1"

?width 0.3

?pts list(0:0 5:5)

?endType "octagon"

?cvId geGetEditCellView()

)

 This is the same code I use in both versions of Virtuoso but in IC6.1 it makes skew edges at either end of the path.

My DBUperUU is set to 1000.0, which is the same in both versions.

Thank you,

Eugene 

Eugene,

I hadn't really understood what you'd meant by "skew edges". Also, you'd not said that the path was at 45 degrees, which I think is key to the issue.

Anyway, I've reproduced the issue. What I did was use the code you used above, and then convert the path to a polygon. Using this SKILL code:

{foreach(map point append(car(geGetSelSet())~>points car(geGetSelSet())~>points)
 when(cadr(point) println(mapcar('difference car(point) cadr(point))))) t}

with the polygon selected, it displays the differences between successive points (it repeats the point list twice, to allow you to get the difference between the last point and the first - I was being lazy). In IC5141 I get:

(-0.07 0.07)
(-0.142 0.0)
(-5.0 -5.0)
(0.0 -0.142)
(0.07 -0.07)
(0.142 0.0)
(5.0 5.0)
(0.0 0.142)
(-0.07 0.07)
(-0.142 0.0)
(-5.0 -5.0)
(0.0 -0.142)
(0.07 -0.07)
(0.142 0.0)
(5.0 5.0)

You can see all these deltas are either orthogonal (one of the x or y is 0.0) or 45 degree (the absolute value of the x and y are the same). With IC615, I get:

 (-5.0 -5.0)
(0.001 -0.143)
(0.07 -0.07)
(0.141 0.001)
(5.0 5.0)
(-0.001 0.143)
(-0.07 0.07)
(-0.141 -0.001)
(-5.0 -5.0)
(0.001 -0.143)
(0.07 -0.07)
(0.141 0.001)
(5.0 5.0)
(-0.001 0.143)
(-0.07 0.07)

As you can see, a number of the "orthogonal" deltas are not quite orthogonal - the x or y is +/-0.001

However, in IC616 (ISR1), I get:

(-5.0 -5.0)
(0.0 -0.142)
(0.07 -0.07)
(0.142 0.0)
(5.0 5.0)
(0.0 0.142)
(-0.07 0.07)
(-0.142 0.0)
(-5.0 -5.0)
(0.0 -0.142)
(0.07 -0.07)
(0.142 0.0)
(5.0 5.0)
(0.0 0.142)
(-0.07 0.07)

So it appears to be fixed there (I couldn't find any reports of this, so maybe it was uncovered during some product validation). The same is true if I create the shape in IC615 and then view it in IC616 - it's fixed.

However, I just found that the interactive "Convert to Polygon" seems to be broken in IC616 with this shape (it was OK if I used dbConvertPathToPolygon instead). So I've filed CCR 1185948 for that issue.

Kind Regards,

Andrew.

Hi Andrew,

Thank you for the great reply! Interesting idea taking the difference of neighbouring points. I was just running Calibre DRC which gives a warning for non-orthogonal/non-diagonal lines that it calls "Skew Edges". 

Thank you also for verifying this problem for me, I will try and get the IC616 release.   

 Eugene