Project Updates

New developments for the software suite including CrossMgr, RaceDB and SeriesMgr.

RaceDB: New Licence Check Screens

posted Dec 13, 2017, 3:08 AM by Edward Sitarski   [ updated Dec 14, 2017, 5:45 AM ]

RaceDB 1.32.62 now has screens to help with license checking.

The first new screen allows you to configure which categories require license checks (for example, beginner categories may not required license checks).
From the "Competition Dashboard", press the "Check Licenses" button and select which Categories require license checks, and any special note about each one.  For example, in the note, you can list the category codes printed on the license which can race in that category.  For example, "RME codes only".
You can also specify a note which is displayed for all License Checks.  For example, "Riders with a license issued outside the US and Canada requires a letter of permission from their federation."

License Checks are configured at the Competition by Category, so it is easy to configure the specific requirements of each Competition.

For categories requiring a license check, a new License Check step is presented in the Participant screen after the Category has been established.  This step is must be completed before the Bib number is shown.

The License Check step present all the rider's information and a general checklist of what to check on the license (valid year, signed, photo id, name, gender, license code, UCI ID and team).  The screen also shows any notes about the rider, the specific Category Note and the General Note (specified in the "Check Licenses" screen).
If any of the information is incorrect, it is easy to changed it by pressing the "Fix" buttons conveniently located next to each line in the checklist.  The "Fix" buttons open the appropriate screen required to update the incorrect information for the rider.

Pre-reg import also accepts a new field called "License Checked".  This allows you to initialize the "License Checked" status from a pre-reg Excel import.  It is also output when you export Participants in Excel.

Finally, the "Check Licenses" configuration screen supports an export/import to Excel.  This makes it easy to copy configurations from one Competition to another.
Of course, the "Check License" info is included when you do a "Copy Format" from the Competitions screen.

These new screens streamline the process for reg staff or officials to perform comprehensive license checks.
Rather than making notes and updating the information later, the new screens allow errors to be fixed online at registration so that all information is correct.

CrosMgr: 2.20.0 Released

posted Nov 25, 2017, 10:10 AM by Edward Sitarski   [ updated Nov 25, 2017, 10:15 AM ]

CrossMgr 2.20.0 is now the release version of CrossMgr.
There are an incredible number of new features, too numerous to mention.

As usual, CrossMgr 2.20.0 is backwards-compatible with previous versions.  Just upgrade to the new version and you are good to go.

Thanks for all the great suggestions and ideas!

CrossMgr: New Announcer's Screen

posted Nov 12, 2017, 8:44 AM by Edward Sitarski   [ updated Nov 12, 2017, 9:37 AM ]

CrossMgr now supports a screen specifically designed for race announcers.
This screen is available in a web page ("Web/Index Page") and is real-time updated from current race information (using web sockets).
It is also available as a screen in CrossMgr itself.

The Announcer screen specifically addresses the needs of a race announcer by showing:
  • Current and Expected race positions by lap (expected positions are shown greyed-out).
  • Time gaps for all competitors
  • Estimated Time of Arrival (ETA) for all competitors.  ETA is color-coded in the last 15 seconds (dark-to-light).
  • One-click switch between categories for multi-category races.
  • ETA for all category leaders is always shown - even if that Category is not currently shown.  ETA is color-coded in the last 15 seconds (dark-to-light)
  • Color-coded chase groups with composition.
This gives announcers full knowledge of the current race results as well as what is expected in the next lap/

Give it a try in the CrossMgr simulation.  Do a "Tools/Simulation" and start a mass-start race.  Then do "Web/Index Page...".  After the page opens in your browser, select the "Browser" at the top..

Available in CrossMgr 2.10.49.

CrossMgrVideo: New "Time in Frame" feature

posted Oct 19, 2017, 8:49 AM by Edward Sitarski

CrossMgrVideo now supports a "Time in Frame" feature.  Requires upgrading to the CrossMgrVideo 2.10.2 and CrossMgr 2.10.43.

CrossMgrVideo captures frames of the finish line triggered by CrossMgr.  It uses inexpensive USB cameras.
The program makes it easy to access and playback small videos of rider finishes.  This is critical to check for close finishes as well as looking for interference.
Because it uses a frame buffer, it records a few second *before* and *after* the rider is detected.
It can output video, individual frames or a "finish strip" which is similar to the output of a scan-line camera.

CrossMgrVideo is particularly helpful when triggered by CrossMgr RFID.
Both active and passive RFID systems have a window of inaccuracy where chip times are reported randomly.  Due to chip mount, orientation to the antenna etc, reported chip times vary from the "true" time. Close finishes must be checked visually.

The "Cadillac" solution is a high-speed line-scan camera, but these are very expensive.

CrossMgrVideo makes it easy to check close finishes with inexpensive usb cameras and a standard laptop.   It is limited to 25 frames per second, however, there is no limit to the number of CrossMgrVideo cameras you can use.

In addition to capturing finishes, CrossMgrVideo has a number of analysis features.
Right-click on the finish strip to get to a frame.  Then, click on the "speedometer" button and a wizard allows you to compute the speed of the rider in the frame.

To get the speed of a rider's finish, you must first identify the leading and trailing edge of the front wheel.  This is important to get a reference dimension.  It is convenient that bicycle wheels are all almost exactly 670mm in diameter.
After establishing the wheel edges, pressing Next shows the next video frame.  Identify the front wheel edge in the new frame you can get the rider's speed:
Pressing "Next" shows a final screen where you can get the rider's time anywhere in the frame.  A horizontal line is shown to make it easy to line up the wheel with where the rider would cross at the finish line.
This final screen allows you to get an accurate time of when the rider actually crossed the finish line.
Of course, this calculation relies and the previous two screens.

But... how accurate is it?

Of course this is not a real-time system.  Here is my best guess reasoning about errors.

  1. Wheel size estimation.  As this is being done visually, it could be off by a pixel.  If the wheel is 100 pixels on the screen (about 1/12th of the frame), that's a 1% error.
  2. Wheel movement estimation.  This is also done visually and could be off by a pixel.  If the number of pixels moved between frames is 100 (by adjusting the number of frames used), and assuming +/- one pixel, that's another 1% error.
  3. Speed up/slow down of riders between frames.  If a rider was breaking hard or accelerating, the speed could change between frames.  It would be reasonable to expect that a rider could change speed at 0.1 km/h every 1/25 seconds (frame rate).
Combining the errors, we get 2%, or about 1/50.  This means that for speeds around 50km/h, it should be accurate to +/- 0.5km/h.(0.55km/h if we include uncertainties in the current acceleration/deceleration).

The accuracy of time in the frame is a bit more difficult.  As the frames are 1/25 second apart, 2% of 1/25 is 0.008 seconds.

Of course, there are errors in estimating when the wheel hit the line in the frame.  All in, an upper bound of +/-0.01 seconds of error seems reasonable (about 1/100th of a second).
With this system, finishes within 0.01 seconds of each other should be considered ties.

Not a fancy scan-line camera, but pretty good for the money.

CallupSeedingMgr: Now supports UCI ID

posted Oct 19, 2017, 6:43 AM by Edward Sitarski

CallupSeedingMgr has been upgraded to support the UCI ID.

The program makes it easy to compute callup orders for CycloCross and Mountain Bike based on UCI points (with rankings downloaded from the UCI site).

License codes and Names (both perfect spelling and sound-a-like) can also be used if the UCI ID is not available for identification.  CallupSeedingMgr also shows warnings if the name does not match the UCI ID (important to detect an incorrect UIC ID).

As always, CallupSeedingMgr supports multiple callup criteria.  For example it is easy to configure callups based on:
  1. UCI Points
  2. National Series Points (if no UCI points)
  3. Last Year's Results (if no UCI or National points)
To use the program, create a spreadsheet with a Registration sheet of the riders in the race.
Then, create callup criteria sheets (as many as you with).  The program will create a new Excel spreadsheet with the callup order based on all the criteria given.

Rank is preserved within the criteria.  In the above example, if two riders are tied on UCI points, this order will be preserved - even if one has more National points.  This is because there are additional criteria used to break the tie that are reflected in the rank.

RaceDB: CrossMgr publish bug fixes in RaceDB 1.32.46

posted Sep 1, 2017, 6:19 AM by Edward Sitarski

A bug was introduced when adding the "relegation" field to the CrossMgr publish 
This bug prevented uploading CrossMgr results back into RaceDB.

The bug has been fixed in 1.32.46.
If you are running RaceDB and are publishing results from CrossMgr to RaceDB, you will need to upgrade.

CrossMgr: Better Real-time Web Results

posted Aug 26, 2017, 6:40 AM by Edward Sitarski

CrossMgr 2.10.30 now supports better real-time web results.
At race site, when connected to the CrossMgr web server, new race results are now "pushed" to the web page as soon as they are recorded.
Previously, it was necessary to press the "Refresh" button on the results page to see the latest results.

The automatic update is less confusing to new users (and announcers) who were concluding that the results page was broken when it didn't update after the riders went by.

To see a demo:
  1. Start CrossMgr
  2. Do Tools/Simulate Race... - select "Mass Start Race"
  3. Do Web/Index Page, and select "Simulation" to get to the results page.
  4. When the page opens up in the browser, watch how newly recorded results appear automatically in the animation and in the results.
Of course, pressing the "Results" button (or doing a browser refresh) will also update the results.

To see a demo with a tablet:
  1. Make sure the CrossMgr computer and the tablet are on the same local wifi network.
  2. Do Tools/Simulate race... - select "Mass Start Race"
  3. Do Web/Index Page
  4. Press the "Share" button at the top of the web page.  This will create a QR-code of the page.
  5. Point your tablet at the computer screen, and use the tablet's QR-code reader to get to the page (on Android, see here).
  6. When the web page appears on the tablet, select "Simulation" to bring up the results.
  7. Watch how newly recorded results automatically appear on the tablet page.
Because this feature is accomplished with a web socket server, it will only work at the CrossMgr race site.
If the results page is served from a public web site (say, if the page is automatically ftp'd to it), then the refresh button will have to be used.

CrossMgr: Now with Web-based Lap Counter

posted Aug 26, 2017, 6:25 AM by Edward Sitarski

CrossMgr 2.10.30 now supports a web-based Lap Counter.
This allows you to use a tablet mounted on a stand as a lap counter.
The tablet is automatically controlled by CrossMgr, which talks to it over a local wifi network.

The web-based Lap Counter is easily accessible from the Index web page from CrossMgr.
The Lap Counter page responds to the current running race, so, once you bring it up, it will reset itself and follow all the races throughout day.

This feature provides more flexibility over the previous Lap Counter screens in CrossMgr, which required a monitor or a projector (of course, in some situations this still works better).

To see a demo of the web-based Lap Counter:
  1. Start CrossMgr
  2. Do Tools/Simulate Race..., press "Mass Start Race"
  3. Do Web/Index Page.
  4. On the web page, select Lap Counter.
  5. A Lap Counter will be displayed on the web page, exactly like the CrossMgr screen.
  6. To return to the Index page, use the "Back" button on the browser.
To see the Lap Counter on a tablet:
  1. Make sure your CrossMgr computer is connected to a local wifi network.
  2. Follow steps 1-3 if you have not done so.
  3. On the Index page, press the Share icon at the top.  This will create a QR-code of the Index page.
  4. Point your tablet at the computer screen and activate a QR-Code reader app (on Android, available here).
  5. After getting the Index page up on the tablet from the QR-Code, choose "Lap Counter".

CrossMgr: Better synchronization with TT Countdown Page

posted Jul 11, 2017, 6:24 PM by Edward Sitarski

For a few years now, CrossMgr has supported a TT Countdown page for Time Trial races.
This page shows each individual rider's bib, name and team, and a countdown to the start with proper "beeps" on 10 seconds, then 5, 4, 3, 2, 1 and 0.

This makes it easy to manage starts (especially on 30 seconds).  By showing the rider's bib, name and team, it makes it much more difficult to make a mistake.  With the beeps doing the countdown (just like the pros!), officials or volunteers can focus on other issues.
It also makes it easy if there are irregular gaps or many categories.

This feature has grown increasingly popular using tablets for the start countdown device.
In the past, it was important to synchronize the clocks on the computer and table.  This can be difficult to get closer than a few seconds.

Technically this does not matter much.  As long as the start and finish clock are the same for all competitors, all the placings stay the same.  However, aesthetically, the time should be accurate.  And, it is important, say, for tracking the fastest time on a course.

CrossMgr and its TT Countdown page now follow a protocol that can synchronize the TT Countdown and CrossMgr within a few 1,000s of a second.
This greatly improves the accuracy of the times.

Available in the latest version of CrossMgr.

SeriesMgr: Support for Team Series

posted Jun 21, 2017, 7:31 AM by Edward Sitarski   [ updated Jun 22, 2017, 5:05 AM ]

The latest version of SeriesMgr (v2.8.16) now supports team series results, available in a new "Team Results" screen.

Currently, Team Results are computed based on Points, and uses the same Points-for-Place scoring for individuals (including any points specified for participation and DNF).
This is all configured in the "Scoring Criteria" screen, which includes a field for the maximum number of team member results to count per race in the "Scoring Criteria" screen.

Mid-season upgrades have no effect on Team Results, which are simply computed from team members results in each race.

There is also a convenient "Team Aliases" feature.  This screen allows you to define alternate team spellings.  Doing this in the aliases screen is more efficient than fixing up inconsistencies in multiple CrossMgr or Excel race files.
See the "Team Aliases" screen for more explanation.

I am looking for feedback on this feature.  I checked a number of examples I could find on the internet, and what I did was consistent with them.
If you have some ideas, let me know!

My initial attempt took the most straight-forward route possible.
Using Points is the easiest.  Combined results based on time leads to problems if the minimum number of team members does not show up to an event (perhaps should be counted as non-participation in the event?).

Update - Some initial feedback:
  • Provide ability to exclude certain Categories from Team Results (for example, beginner categories).
  • Score a Team TT, by taking the time based on the Nth rider in a team finish.  The N is specified by Category.  Perhaps a "compassion" option to take the last team member's time if the team was smaller than N.
  • Score Teams based on total time of top N team member finishes.  This involves handing more complicated cases (team is too small, missed events in a Series, tie breaking, etc.).  Would need to look at rules for stage races.
In all cases, consider porting functionality to CrossMgr.  Perhaps just Team TT and Team based on time only (no points).

1-10 of 218