In opamp, the vertical routing on m2 (pink) is not coming out at the same coordinate as the end point of the bottom m1 horizontal routing (cyan). The other routing on m3 (blue) uses the port coordinate as the routing target, thus missing the centerline and placing a via at the wrong location.
The code for this block haven't changed since the original OpenFASOC repository (https://github.com/idea-fasoc/OpenFASOC/blob/d6a34519db74d3650203c00206da276d298d5fbb/openfasoc/generators/glayout/glayout/flow/blocks/opamp/diff_pair_stackedcmirror.py Line 74~76). So I suspect this regression is caused by the c-route command that created the m2-m1 routing, or maybe it's from the upstream changes in GDSFactory. Currently in the repository, the c-routing is creating many wrong-looking via placements. Need more investigation.
A temporary fix is added to PR #88
In opamp, the vertical routing on m2 (pink) is not coming out at the same coordinate as the end point of the bottom m1 horizontal routing (cyan). The other routing on m3 (blue) uses the port coordinate as the routing target, thus missing the centerline and placing a via at the wrong location.
The code for this block haven't changed since the original OpenFASOC repository (https://github.com/idea-fasoc/OpenFASOC/blob/d6a34519db74d3650203c00206da276d298d5fbb/openfasoc/generators/glayout/glayout/flow/blocks/opamp/diff_pair_stackedcmirror.py Line 74~76). So I suspect this regression is caused by the c-route command that created the m2-m1 routing, or maybe it's from the upstream changes in GDSFactory. Currently in the repository, the c-routing is creating many wrong-looking via placements. Need more investigation.
A temporary fix is added to PR #88