Hi, we got 2 antenna violations after running openlane. We cannot find where violation in the report which is attached. Could someone please let us know how we might open the report and debug it? Thanks!

The errors are marked with asterisks.

Net - io_in[10]
  mprj  (user_proj_example)  io_in[10]
[1]  met3:
  PAR:   72.78  Ratio:    0.00       (Area)
  PAR:  400.21*  Ratio:  400.00       (S.Area)
  CAR:   72.78  Ratio:    0.00       (C.Area)
  CAR:  400.21  Ratio:    0.00       (C.S.Area)

and

Net - io_in[7]
  mprj  (user_proj_example)  io_in[7]
[1]  met3:
  PAR:   73.14  Ratio:    0.00       (Area)
  PAR:  402.12*  Ratio:  400.00       (S.Area)
  CAR:   73.14  Ratio:    0.00       (C.Area)
  CAR:  402.12  Ratio:    0.00       (C.S.Area)

That's probably close enough that it won't be a problem, but I don't know how to waive them.

Thank you, @Mitch Bailey! We do not understand why we have antenna errors for those ports. They are not the longest nets either. For a design with the same pin assignments and floorplan, by just changing period, we could have antenna errors on different ports.

Look at the ratio of gate area to the total connected licon, met1, met2, and met3 area. Increasing the input gate size might help.

Hi Mitch, I am Jake's project partner. How would we go about increasing the gate size? By specifying a larger fan-out?

Hey Chris. Sorry, I have no clue, but a larger fan-out might work.

@Jake Ke you can pretty much ignore antenna violations as they should only affect yield. they do not block tapeout submissions.

Okay. Thanks!