Version 2.1: General Improvements and
Enhancements

New 'Create Races and Stages' Menu

A new Event context menu provides the ability to create heats and
stages for one or more selected events based on any supported
progression system. The action:

1. Creates the qualifying and final Stages (heats, semi-finals, etc.) according to a selected progression system
2. Creates the races in each Stage needed to accommodate the number of entries.
3. Set the proper timing format for each race (time trial or sprint)
4. Assigns each entry (Crew) to a race lanes in the first qualifying round seeded in the order they are listed as children of their event.
5. Adds AdvanceSelectors to any qualifying stages to enable the race day progression of crews, once the results are available.

One note: the event must have no Stages for this menu option to be enabled.

To support this function, the whole progression system management component was rewritten and now includes five standard progression systems from USRowing and FISA and two custom progression systems are supported. Here are the descriptions of the behavior of each of the systems.

The new progression system component allows the flexibility to tweak and tune these basic progression systems, however this capability is not yet exposed in the interface.

Gender-Filtered Team Points Reports Options

The generated team points reports can now be filtered by the event's gender attribute: female, male, mixed, and all genders. The report menu has been updated to allow for this selection:

New team points computation added

A new team points computation called 'Winning Boat Size Point
Computation' has been added. Like the other computations, this one is selectable as an attribute of the Regatta object
in the properties tab.

Here's how it works.

1. It uses the boat size as the number of points earned. Boat size is based on the number of rowers.
2. It only awards points to the winning crew.
3. It doesn't award any points to composite crews.
4. It awards points to races in flight and final stages, no others.
   In Workbench, heats that are finals are called flights.

Support for alternate/spare crew members

Spares can now be added to a crew's member list.

Spares can be swapped into the boat lineup using two new context menus, one for the Spare Member ...

... and one for the Member

FinishLynx .evt file export

To make age-based seeding processes easier, crews can now be sorted by average age. Clustering crews by age in final-only flights is common for masters races.

When creating a new crew entry in an event, the crew wizard now allows the inline creation of additional athletes without leaving the wizard. Previously, all athletes needed for a crew had to have been created prior to starting the crew wizard.

A new page has been added to the end of the New Crew wizard that optionally allows the assignment of the newly created crew to an existing race in any stage of the event. The new crew being added is highlighted in yellow and the tree supports drag and drop and context menus for renumbering the lane or bow numbers.

Sometimes during the import of captured splits, a crew's information (event, stage, race, lane) cannot be matched with a crew in Regatta Workbench. In cases where the crew is not already entered into Workbench, a 'New Crew...' button has been added that spawns the New Crew Wizard. Upon completion of the wizard, Regatta Workbench will attempt again to find a match for the captured data, this time including the newly added crew. When spawned during import, suggestions for race and lane are provided to the 'New Crew'  wizard that match the unresolved crew's.

The FinishLynx user interface provides a limited number of characters in its race name field, so the race number and race time were moved to the front of the exported string. For example,

'Mens Masters 1x (AA-B) Flight @ 12:00 AM  changed to '11a @ 12:00 AM Mens Masters 1x (AA-B) Flight'

The newly released SWT date time field now provides more standard and intuitive behavior than the previous custom widget.

Heat Sheet Report updates:

• Now supports any number of race course lanes from 2 through 8. Previously only 3, 5 and 7 lanes were supported.
• Added regatta logo image to title area
• New page footer content: regatta name, regatta home page web site hyperlink and time printed
• Now customizable in the Report Design editor
• Heat Sheets with 2 - 4 lanes are printed portrait, while those with 4+ lanes are printed landscape. This is easily changed in the Report Design editor by changing the Master Design object's page orientation attribute.

Miscellaneous Bug Fixes and Updates:

• Now running on Eclipse 3.3 base with Europa plugins.
• Fixed bug in New Regatta Wizard that prevented the finishing and creating the regatta. Thanks to Kevin Gant, a member of the Chesapeake Boathouse in Oklahoma City, for finding and reporting this bug.
• New sprint timer report which print postcard sized forms for capturing and computing manual times for each racing crew. The report is designed to print on Avery Template 8387 stock, 4 postcards per 8.5x11 page. Each postcard is 5.5"x4.25" and will fit into a 4x6 index card box.
• Fixed a bug in the default values for 1st, 2nd and Last call. 1st and Last call were reversed. Now the default offsets for the 1st, 2nd and Last Calls are 40, 30 and 20 minutes. These values can be customized in the Venue's Primary Launch Site entity.
• Fixed bug that occurred when Organization had null 'name' attribute.
• The New Crew Wizard now defaults to having no organization.
• Fixed font issue on dynamically generated label reports. These reports were printing as centered, italicized for all exported types, except PDF.
• Fixed bug where composite crews were receiving team points. Thanks to Steve at Regatta Central for finding this bug and the USRowing Rule that covers this: "Rule #5-204  (2006 USRowing Rules of Rowing, p. 59): Composite crews are those that include competitors from more than one club. Such crews shall be ineligible to receive points or other scores used to determine team trophies or awards, including those described in Rule 5-307.  Once a crew has been entered as a composite crew, it shall remain so, regardless of subsequent substitutions."

For many Masters events, regatta committees group the crews by age in separate final-only flights within a single event. If specified either in the New Regatta Wizard

or in a menu option,

Regatta Workbench now will group Masters athletes by age in separate flights. The heuristic's threshold for minimum number of participants in a race is 3. The goal is to get a reasonable starting point for the next stage of manual refinements.

New Component

Regatta Workbench

New feature

Regatta Workbench