Hello, I was doing local lvs for my design . I am getting property error.

@THANZEEM MUHAMMAD A Looks like there are size errors.

Netlists match uniquely with property errors.
sky130_fd_pr__res_generic_l1:9 vs. flashadc_0/sky130_fd_pr__res_generic_l1:4:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:7 vs. flashadc_0/sky130_fd_pr__res_generic_l1:5:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:6 vs. flashadc_0/sky130_fd_pr__res_generic_l1:2:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:2 vs. flashadc_0/sky130_fd_pr__res_generic_l1:1:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:5 vs. flashadc_0/sky130_fd_pr__res_generic_l1:3:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:4 vs. flashadc_0/sky130_fd_pr__res_generic_l1:7:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:3 vs. flashadc_0/sky130_fd_pr__res_generic_l1:6:
 M circuit1: -755914244   circuit2: 1   
sky130_fd_pr__res_generic_l1:1 vs. flashadc_0/sky130_fd_pr__res_generic_l1:0:
 M circuit1: -755914244   circuit2: 1

When sharing results of manually executed LVS, please include the netgen command used. I suspect that you are doing SVL (with the source first and the layout second) instead of LVS. I suspect that the

li

resistor does not have an M value in the schematic. This may be a problem with the

res_generic_l1

primitive device.

I would like to see the netlist because whatever the problem is (or isn't), netgen should not produce a huge negative number, suggesting that it missed initializing a variable representing M. Normally it assumes M =1 if M is not present. Swapping schematic and layout from the usual order may have exposed a coding error in netgen.

sir how can we debug this property error @Tim Edwards, @Mitch Bailey?

Can you share your netlists and the command that you used to run netgen or is this a proprietary project?

greeting sir @Mitch Bailey attached are the spice files of xschem and magic for the example nor_gate : where the nor_2.spice is the xschem generated spice file and nor_mag_jj.spice is the magic spice file after layout the command used is "netgen -batch lvs "nor_mag_jj.spice nor_mag_jj" " nor_2.spice nor_2" sky130_setup.tcl ", and this is not a proprietary project we as a group of students together learning this open source tools .

@Mohammed Zeeshan Great! looks like lvs is passing now.

@Mitch Bailey YES it is passing the lvs as you mentioned however this no property warning how should we debug are there any potential ways to get rid of the no property warnings and can you please specify the reason why it such warning occurs

@Mohammed Zeeshan Please ignore the no property warning. The sky130A_setup.tcl file contains directives to ignore these properties. However, if the property doesn’t exist, a warning is generated when the netlist is read in.

@Mitch Bailey sir is this property warning do effect the gds after successful post layout simulation and then writing the gds?

@Mohammed Zeeshan Sorry, I’m not involved in post layout simulation, but I think that is a reasonable assumption.

@Mitch Bailey okay sir thanks for the response really appreciated sir!

Also, some of those parameters are probably used in the simulation version of the source netlist.