You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
In competitive.py, line 103 there is a shared implied constraint of 3 of top 5 honors for a suited overcall. This is bogus and causes problems with hands like:
There is no way this should be passed out by either north or south as the autobidder suggests. A sixth trump is every bit as good as another honor. Maybe the rule should be 3 of 5 or 2 of 3 with 5, or any 6+ that isn't already a preempt? Unfortunately I don't understand the engine enough to know how to code that.
North going to 1NT over west's raise to 1S is intriguing. It seems like the kind of bid only a computer could make but it seems to work well here (-50 vs. -80).
The text was updated successfully, but these errors were encountered:
In competitive.py, line 103 there is a shared implied constraint of 3 of top 5 honors for a suited overcall. This is bogus and causes problems with hands like:
http://www.saycbridge.com/bid/11-93875b35e6c6ca629d2c4383dc:P,1D,P,P,1H,1S,1N,P,P,P
There is no way this should be passed out by either north or south as the autobidder suggests. A sixth trump is every bit as good as another honor. Maybe the rule should be 3 of 5 or 2 of 3 with 5, or any 6+ that isn't already a preempt? Unfortunately I don't understand the engine enough to know how to code that.
North going to 1NT over west's raise to 1S is intriguing. It seems like the kind of bid only a computer could make but it seems to work well here (-50 vs. -80).
The text was updated successfully, but these errors were encountered: