- Scoring a Pairs Event
Frequently Asked Questions
Frequently Asked Questions
To upgrade to the latest version, follow the same route through 'My EBU' as if downloading for the first time.
If you need to check whether you have you have the latest version (without having to visit this website), in EBUScore itself, click on the “Administration” button on the Main Menu, then on “Check for Updates”.
EBUScore hangs when checking Bridgewebs for pre-uploaded events, when there is a gap in event numbers.
Error in printing checkslips when there is both a missing pair and an artificial adjustment.
Error in calculating split / weighted scores in PaB/Hybrid scoring.
Introduction of temporary UMS code 90, for use only in the August 2018 EBU Summer Festival.
Bridgemate Control Software:
Compatibility with BCS version 3.6.9 ensured.
Option added to enable BMs to “verify lead card against hand records”
Options to apply either a 50% handicap (as previously used by PairsScorer & EBUScore) or 100%.
EBU Master Point Ranks:
Distinction recognised between genuinely “unranked” players, and players with ranks withheld, or with MP records held by other NBOs.
For purposes of stratification or handicaps, where EBUScore is unable to determine the rank of a player, such a player will not receive any potential benefit.
Error exiting “Irregular Movement” screen corrected.
Error overwriting pair numbers in Scoresheets (indirectly caused by too many events in the Event File).
(error corrections on 6th & 16th November)
Revised way of recording NGS exemptions: Either or both players in a partnership can now be exempted (and only one pair can be eligible for exemption)
Where a session has been pre-created, or if a session has already been uploaded for the same date, there is now an option to over-write existing session, or to upload as a new event.
There is now a facility during a session to upload “Live Ranks” to BridgeWebs.
Recognition of new ranks (Star Grand Masters)
NB previous versions of EBUScore may not cope well with “stratification” when players of these ranks are involved.
Possible correction of error with BridgePad names entry.
Error corrected when creating SwissTeams ClubPrint file in HTM format.
New source of EBU membership database. This database is updated daily.
(Old source will still be updated on a less frequent basis, so that old versions of EBUSCore will continue to work)
Improvement on reporting of Swiss Teams triples for Pianola
Correction of number of competing pairs in XML file for Pianola
Renaming of text file reporting creation of XML file, to avoid confusion.
ArcScorer added to the list of alternative Wireless units.
Swiss: Potential Match adjustments extended when a 30-0 VP Scale selected.
Reintroduction of UMS code 11
(novice events, not eligible for UMS exemption. No Master Points, no NGS)
Relocation of WBU membership database.
Error message re-writing names to BCS
Amendment of EBU Default Bridgemate settings
Scoring method for new Teams events always defaults to IMPs (avoids annoying message when previous event was To8)
Improved (but not perfect) analysis of names typed with middle initials, etc. (e.g. Arthur C Doyle; Arthur Conan Doyle, etc.)
Creation of EBU UMS files:
The launch version of EBUScore is almost identical in functionality to the Jeff Smith Suite.
There are obvious 'cosmetic' changes: displaying 'EBUScore' as the name of the product, etc.
Other changes are of little relevance to most users. Most relate to increased capacity, e.g.:
These, and other internal changes, have meant that EBUScore Data files are incompatible with those of the equivalent Jeff Smith files. Please see here for more information.
Unsurprisingly, some of these internal changes have led to unforeseen bugs creeping in. We hope that these have mostly been resolved in the following release, 1.1.2.
Retention of PIDs when uploading/downloading player database to/from Bridgewebs.
Code 08 added to UMS codes.
NGS only: This is used for events for which payment and Master Points are processed independently, such as leagues.
A warning now appears in some situations when the UMS code selected appears inconsistent with the Master Point settings.
(NB the UMS code is principally a Payment code, not a Master Point code. Although the two may be related, you need to select those independently - don't assume, for example, that if you select UMS code 50, Master Points settings will automatically be set to be “Blue Points”)
Bug Correction: Too many movements in PSUserMovements.txt caused error. Error corrected