Creating via in a given area

I faced the same problem，can someone help us？

The reason why the original question didn't get answered was mainly the lack of information provided (clearly nobody reads the forum guidelines), and yours is similar. In practice I have limited time to chase people to provide sufficient information (and I was on vacation when the original post came in).

I just tried it (in IC618 ISR5) and if the area specified is too small, then I get vias which extend outside of that area (e.g. if not wide enough to accommodate a single via width meeting the overlap rules).

So, I suggest you post:

1. Which sub-version you're using ( getVersion(t) will tell you this)
2. Your code, so we can see what you're doing
3. A screenshot showing the area you are trying to fill and what the result is

The original poster (Karthik) might want to do the same too so his question can be answered.

Andrew

Hi Andrew，

sub-version I am using is "sub-version  IC6.1.7-64b.500.21 ".

the selected polygon is hilight in the pic.

the lpp used in pic:POLY METAL1 METAL2.

the vias are unexpected on the POLY and METAL1 in the left of the pic.

My code:
cv=geGetEditCellView()
tf=techGetTechFile(cv)
constraintGroupId=cstFindConstraintGroupIn(tf "default")
viaOpts=viaGetViaOptions(constraintGroupId)
viaGenerateViasInArea(geGetEditCellView() css()~>points viaOpts ?topAndBottomLayers list("METAL1" "METAL2"))

But,when I use viaGenerateViasAtPoint like below,
viaGenerateViasAtPoint(geGetEditCellView() car(css()~>points) viaOpts ?topAndBottomLayers list("METAL1" "METAL2"))
it work fine.
thanks.

I get a similar issue (the unexpected vias are in a different pace in my case) with the version you're using.

Having checked, this seems to be resolved in IC6.1.8 ISR4 IC6.1.8-64b.500.4 (I see the same problem in ISR3 still).

Regards,

Andrew.

I get a similar issue (the unexpected vias are in a different pace in my case) with the version you're using.

Having checked, this seems to be resolved in IC6.1.8 ISR4 IC6.1.8-64b.500.4 (I see the same problem in ISR3 still).

Regards,

Andrew.