luke/netgen - netgen - Gitea: Git with a cup of tea

2 lines

8 B

Plaintext

Raw Normal View History

Found a counterexample which shows that the fast symmetry breaking introduced in revision 150 can result in an incorrect result reporting a bad match where the match is actually good (as proven by running the full symmetry breaking on the same netlist). Because the fast symmetry breaking is orders of magnitude faster for large circuits, and because the false positive result appears to be rare, I have introduced a command "symmetry" to switch methods between fast and full. So fast symmetry breaking can be run unless the result fails on symmetry breaking, in which case the method can be switched to full to see if the problem is a false positive or not. This is not an ideal solution, and some investigation is needed to determine if there is a way to apply fast symmetry breaking without encountering a false positive error.

2020-10-08 15:43:25 +02:00

1.5.157