Full Disclosure Logic

[brownbear]

A question for the techos :)

 

I have written some database structures plus code to logically generate Full Disclosure cards for use in BBO.

 

I have done the work for my normal card where I can generate a file which uses generic definitions (such S1=Suit at 1-Level, S0=cheapest new suit etc.) plus bolt on bidding units which will create a card of 1000 lines - so far.

 

I can change the table definitions and then export a new FD Card.

 

The stuff works but I am now grappling with the issues of different positions and vulnerabilities.

 

I have found that you have to create extra lines of bid definitions which are not intuitive.

 

For instance:

001H=NYYYYYY34812+ | 4+!H | Better suit if 4M/4m Minimum

601HP2C=YNNNNNND00Drury 2Cover 1H 3rd/4th Seat

 

Because the 2nd line exists the first line is ignored because a line starting 60 is expected. It doesn't assume that nothing happens until a Seat/Vul branch is required.

 

What I am after is the processing logic of how Full Disclosure uses the Seat and Vulnerability settings so I can continue to develop the code base without doing things that are not necessary.

 

If anyone out there can help me with this stuff, I would be very appreciative. :o

 

Regards, brownbear

[fred]

If figuring out the answer to your question involves looking at the FD source code (which sounds likely), then I am the only person who might be able to help.

 

But I really do not understand what it is that you are asking.

 

If you want to try to clarify your question via e-mail (fred@bridgebase.com) I will see what I can learn, but I might not get a chance to investigate until early next week.

 

Fred Gitelman

Bridge Base Inc.

www.bridgebase.com