Here comes our mid-year traditional delivery. As usual, we're keeping you tuned with all the visible new things included.

G-Live

A major revamp finally goes live for your race results publications!
Adding to the wide capabilities of G-Live app, we're excited to provide a new graphical and functional layout as a landing page.
A picture worth thousand words:

This translates into new options in the event publication screen, mainly:

• a cover picture file, which can be an external URL or a relative path if you chose to upload it in the event folder
• whether the leader board view is activated

This remains optional, as for some events you may not get an appropriate leader board for example. Or you prefer keeping the light version of the app and care yourself about the surrounding.
The race logo picture will be used now for display on the landing page, and also on the athletes result form.

Note that we aim this also as a replacement for the external header, as there's now a place for race name and logo. We're aware though you'll still want to have your timing company branding somewhere so we keep looking for the ideal options making all that fit it naturally.

Other improvements

A new generic sharing button is now in place for an athlete result.
The behavior is let to the browser, for example on a smartphone it will provide a list of possibilities based on installed apps.

 

Tournaments

Points

• you can specify that point values are originating from the secondary classifications. These are classifications like mostly found in cycling, but available for a custom purpose. They can be made of sub-rankings like an intermediate sprint, or for points attribution on a given lap.
• now there's an option to allow for an automatic calculation of points. Just be aware it can have detrimental effects on performance depending on the volume of competitors and the kind of formula in place. Remember also you can deactivate it if you need to make some manual corrections at some point.

Rankings

Team rankings

Secondary classifications

Tie breaking

Ranks by category (age group)

Ranking without timing

Split points

We've introduced a new option for an intermediate split point, to allow integrating a split time on a participant regardless its assigned race.
This is to deal easily with scenarios when participants are allowed to chose their route after the start.
A split point 40km can be bound to race 55K, somebody initially belonging to race 20K or to no race at all won't see its passage rejected because he's not on the expected race. Then an automatic race assignment rule can be triggered (that says, if participant split time for 40km location is not blank then race is 50K).

Start order

The start times assignment tool (mostly used for time trial races) is now enriched to allow for working on a simple start order, keeping the individual starts untouched.
In this mode it will be working on the existing "Order" data field which can hold random numeric values. Only asking the first value to apply and to increment.

After setting the order you can decide to reassign bib numbers based on it, using the bib assignment tool.

Championships, trophies

In the Championship module, the possible duplicated individuals (when results are merged based on participant names) and possible data inconsistencies are now displayed aside the ranking grid for a better readability and usability.

  

Miscellaneous

Quick passing insertion

Import

Grid filtering

Third party

Those present at our Barcelona conference already had a flavor of it, now it's time to release our 10.1 version which comes as usual with a number of significant improvements.

Let's discover them in pictures and organized by theme:

Ergonomic, Functionalities

Saving grid layout

There's a new menu to store some grid configurations (sorting, grouping, columns) and reapply them later in a quick way. This will fit with some of your work scenarios, for example when you want to recall a layout for printing without relying on a printout template.

Race types

We continue to add flexibility when it comes to bundle different kinds of races in the same event file.

The user interface starts to better reflect that, as you can now tell whether a race follows the overall settings or its own. As of now, not all combinations are technically ready but some useful ones are on the plate:

• You can specify one of the races is handled as a time trial, while other ones remain managed with a mass start
• You can specify one of the races is an individual race, while the main event is a team competition (think about for example a relay lap race with some individuals having their own ranking. This setting is moved as it was previously available from the list of races.

Example of settings: a Vertical Kilometer among some regular mass start races

Participant data

Enhancement of data input for bib numbers representing a team - like after using the merging option on import which concatenates teammate names in a single value. Now the participant entry form displays a multi-line editor with a name on a line.

Time trials

A significant change concerning the way individual start times are handled for a time trial race: now the scheduled start time becomes another independent data field. Consequences and things worth noting:

• The regular 'Start time' information is now fully synonymous with a measured start. So it's easier to check out who's been detected or not on the start line.
• The scheduled start times are no longer overwritten by a start acquisition.
• On the participant list there's now 2 columns, with a combined view in case you make only the main start time column visible (it draws the scheduled start in case there's no value for the measured one).
• Scheduled starts are of course optional, and on the other hand you can still manage a race relying exclusively on the scheduled starts - i.e. with no start time acquisition.
• As soon as measured start times are integrated, a live display of athletes currently in the race will focus only on those having a measured start. In other words it won't assume somebody has actually started simply on the basis of his scheduled time.

Acquisitions - Devices

ITS devices

Decoders from ITS Chrono are now available in the list of equipment you can connect to Wiclax.

URTime Hub

The cloud acquisition for passing data is now compliant with the new hub service from Urtime.

It brings the most efficient access to integrate data, getting it in real time.

NB: it will still be possible temporarily to connect an acquisition to the old Urlive API, by entering the label "nohub" in the name of the acquisition.

Rufus

Wiclax is now compatible with the Cloudbox device from Rufus.

Access to Rufus cloud with the Passing cloud acquisition has been updated for the new API version.

Race Result Ubidium

Ubidium devices can now be set up to sync their data with the Wiclax cloud service.

Further tuning has been made for the local connection to Ubidium devices, as well as for the download of passing data from the Race Result cloud service.

File acquisitions

For file or cloud acquisition, the period selection interface is clarified to distinguish the case of rewind and the case of live import.

Now there's 2 distinct places where the period can be set:

Acquisition purpose

An acquisition can now be typed to behave as a photocell, a start signal or a video finish. In each of these cases the times or passages imported will be processed specifically.

• The photocell or starting gate scenario works like it already does when such a signal is identified by a device. It means that any transponder detection occurring right after the cell signal takes the cell time as a most accurate value. This scenario is with the cell detection placed ahead of the transponder detection. A life duration expectancy can be specified, to fit with the distance between the 2. Things are now more flexible since you can designate any acquisition as a cell regardless of how it transmits its data.
• The start signal option identifies any incoming detection for the acquisition as a gun start, triggering the dialog to confirm its integration and eventually select which starts have to be affected. An option allows for integration without this confirmation, for a case when it's safe and you'd want a very immediate reaction.
• The video finish option tells that any incoming passing data will always overwrite a previously integrated finish time.
• The Kiosk Live screen option can be used to redirect the detection to display athlete's data on a custom Live screen used as a kiosk, i.e. containing some widgets set as 'Kiosk display'.
  

Performances

The system for visual stickers displayed after a competitor passing has been completely refactored. Now ensuring the lowest impact on overall performances whatever their volume. It also drastically limits the risks of grid flickering in the background.

Backup lines

The visual tags for passings originating from the backup line (finish) are now saved between 2 openings of the file. The tooltip on the grid displays the total number of such times processed from the backup.

G-Live and Live screens

Smoother passing display

To deal with groups of athletes crossing the line in a very short time, we've decided to introduce delays before they're sent on screen. So instead of rows too rapidly replaced by next ones and hardly readable, they now get released with an approximate 1s threshold.

There's a limit in delaying of course in case of a very big group.

Focused race

Now you can setup a screen or a screen widget to be bound to the focused race. Displayed data get automatically switched when a new race becomes the focused one.

General classifications

A ranking widget on a custom screen can now display some general classification data (stage races) related to a race in particular, or only men/women.

Sticky leader rows

Applicable to a live screen widget showing recent passings, a new option allows to make it keep race leader rows on top of the list. Option is labeled sticky leaders, value from 1 to 3 rows.

NB: this will work for a finish line, and when a single race is ongoing (focused race, or the event holds only one).

TV Mode

TV Mode is a display mode for G-Live App well suited for a TV display on the race site. It shows a clean result grid with an automated scrolling and a rotation between the different races of the event.

New in this version is the ability to specify which selection of races is to be shown, as maybe the one from the morning is not anymore required. This setting is accessible here in the G-Live menu, clicking on the TV button:

Lap races

We've worked on the standard live screen to make it display more interesting information in the case of a lap race - current lap number, best lap times overall and individual,...

Work still in progress, we're then planning to give priority to the race ranking display over the line crossing information to bring a better monitoring.

Lap number

New option to specify that a race/stage runs with an unlimited number of laps - or said differently, undetermined. This will fit races such as a backyard (last man standing) or a free trial heat.

Lottery

New simple tool to draw some participants from a list of starters/finishers, and print the list.

Maps

In extension of the estimated passing times for split points yet to come, a virtual position sticker is now dynamically displayed on the track and on the race profile. Estimated times are also made available into the splits table.

Note that you need to upgrade your G-Live app files online to benefit from this feature.

Championships

Some default tie splitting rules were applied in case of an equal total of points or time, but it was lacking transparency and flexibility.

Now you will retrieve a list of possible rules for which you can decide about the priority.

And the final ranking grid gives an outlook to how a specific tie case has been decided.

Miscellaneous

Export

New option to export data straight into CSV format.

Maps

Helper feature to quickly assign the same GPS coordinates to several split points.

Intermediate splits

We introduced a new option to specify a format for splits and segments cells in the result grid: time with or without rank and progression information. So that you can make them more or less verbose as you wish.

Licenses

You can now add a stronger protection for license activation on PCs, using a security key associated to the main client account on wiclax.com.

If such a key is entered, it will be required for any activation. Expecting that you are in control of it, either with a physical or remote access to the workstations.

Team rankings

New option to specify which ranks are taken into account when an additional filter is applied to select some competitors - ranks before of after filter is applied.

Détail de la conférence Wiclax 2025 à Barcelone

Emplacement :

Notre conférence aura lieu au cinéma Zumzeig à Barcelone (Espagne), à 2 pas de la gare Barcelona Sants.
Zumzeig Cinema - Google Maps.
Les démos et actualités de notre solution logicielles seront présentées sur grand écran pour un maximum de confort.

Programme : 

La conférence se déroule sur deux jours, sur la base du programme suivant.

Mardi 11 février

9h30 - 10h00 : Accueil des participants au bar du cinema Zumzeig.

10h - 13h30 : première partie

13h30 - 15h00 : restauration au bar.

15h00 - 17h00 : deuxième partie

Mercredi 12 février

9h30 - 10h00 : Accueil des participants au bar du cinema Zumzeig.

10h - 13h00 : troisième et dernière partie

Le détail des différents thèmes abordés sera précisé au tout début janvier.

We're delighted to release this new version 10!

We have focused our efforts on improving core functionality in Wiclax, such as split points and acquisitions. The idea is to make them more intuitive, simpler to use and to provide new functionalities without disrupting your working habits.

For these reasons but also to mark the transition to a new development framework (the invisible work which allows the solution to remain at the cutting edge), we are switching to a new major version.

1. A redesign of the split points screen

As you can quickly see, the screen for split points and segments has a brand new layout on V10.

• start and finish now appear as split points themselves. As a remind, in Wiclax they don't have to be created as such as they always exist for any event.
• the selection buttons at the top will allow you to filter the split points for a particular race. This is particularly practical for an event with a big number of races and intermediate points, which themselves don't belong to all races.

• for each split point you can click on this iconin the right bottom corner of the vignette, to specify some conditions of acceptibility for times received in link with this split point.
  You can define some simple conditions like for a given race any time of day making a net race tame lower than a certain value will be discarded.
  Example pictured: here all times for finish which are lower than 25mn for participants of the 10K will be rejected.

While receiving such a time, a vignette with the rejection reason will appear on screen.

And in the history logs the passing will appear with a specific error icon. Hovering the row gives some detail about the reason invoked for rejection.

If you make a right click on the selected row(s), a menu item offers to re-inject them by bypassing the acceptability condition in place.

That is for a simple scenario, then we've made it versatile and you're free to enter a lot more kinds of conditions here:

A minimum race time between 2 split points
The obligation to be detected at a given split point (located upstream)
Or even some custom conditions
Or else a maximum number of split points without any recorded passing time

2. Acquisitions window - simplified and clarified

One of the changes is about the option 'Retain the last time' which has been moved from the overall level for a better understanding. It's now duplicated at the level of each target potentially linked to the acquisition. That's this new icon with 2 states - black and orange.

Here for instance, the option is off for the finish line. It means that after one integrated passing every subsequent for the same participant will be rejected. For remind, an exception to this rule exists in case the acquisition is defined as a backup line. If Wiclax receives first a time coming from the backup, this time can be overwritten afterwards by another value arriving from the main line if it's anterior (within a limit of 1mn).

Another change is about how you can edit the reception delay allowed after gun start:

Input and understanding of target settings have been enhanced.
As a remind, for such a configuration all times received will be integrated as individual start times, finally keeping the most recent one for the start line.
Beyond 2mn after the race gun start - assuming one is set - new passings received by the same acquisition will be automatically routed to the finish, and this time only the first of them will be conserved. Subsequent ones will be rejected.

3. Enhancements on the passing history logs

This area has been slightly revisited.
All function buttons have been moved on top of the lists.
By default it's now making all the rows visible. And you may click on the 'Filtered mode' button if you want to focus on anomalies only. Or in case you're in a manual or semi-automated timekeeping, to keep a clean list with only rows awaiting for their bib number allocation.

A couple of bugs have also been fixed for a better experience.

4. A simplified system for the bib-chip correspondences

First of all the whole block for the reading filter settings has been displaced in the main Bib-chip correspondance tab. So you get a faster view of the situation in a single tab.
Then we've worked on internal mechanics so that distinguishing between Numerical and Alphanumerical transponder IDs is no more necessary. Hence the options about it disappear, as well as a certain number of complications in data management.

Furthermore: when an alphanumerical transponder was read without having any bib number correspondence in the table, it was translated to bib #99999. And so on for any transponder value in the same case.

We've much enhanced this principle. Now it will instead create a distinct bib number for each unknown ID, starting with value 100 000, then 100 001 and so on. This makes all data recovery scenarios just easier.

5. Podiums report

The podiums printout hadn't evolved since many versions.
We're proposing a more fancy display which associates categories of both genders when age groups are equivalent. So they appear side to side in a more compact and hierarchic way, easier to read out by people in charge of ceremony.

For more complex cases which don't fit for this kind of dispatch, you can still ask for the traditional list printout. The choice is offered on top of the print preview.

Another nice new thing here around:  podium configurations are now remembered for each race independently. So you can for example ask the 5 first athletes overall on 10K but only the 3 first on 5K. Then safely switch between races without loosing this customization.

6. Team ranking settings

In the same spirit than previous enhancements, the form to edit parameters of the team ranking has been completely redesigned to group and display options in a much clearer way.

Yet another often requested feature: the ability to manage multiple team rankings. For instance a Company challenge which comes in addition to the main team ranking.

7. Jerseys for cycling races

We've added the ability to load some jersey pictures on the event file, either team jerseys or classification jerseys. This is a feature essentially fitting UCI cycling races, though could be useful in other contexts of course.

These pictures are used to fancy up the jerseys printout, which can be itself integrated into a stage summary report.

Coming next will be using them as well for web publication, on the G-Live app.

8. Miscellaneous

Certificates

Label fonts are now pointing to the list of Google fonts on certificate templates. This is a nice step forward as they become directly available for the final PDF generation on the Web. In other words, there's no more need to push any .ttf font file manually on the publication server.

Acquisitions

The handy acquisition simulation tool now offers an explicit choice between either the system clock or the Wiclax timer as a basis for times. As a remind, the Wiclax timer is a running time that can take an arbitrary time reference.

Categories

A new menu in the categories management screen, that you can use to populate the list on the basis of category data present in the participant list. Those can come from an import. Beware that the operation might have to be repeated in case any new category is entered on a participant.

Race starts

The input for a race start time can now be completed within the race control panel - no more modal dialog.

Settings for lap races

Refactoring of the laps settings, when multiple races can have their own values (different from what's entered at the overall level). This selector for the application level replaces the detail table which was previously present at the bottom. Both ergonomics and readability enhanced.

9. Acquisitions

Race Result UBIDIUM systems are now integrated.
Feibot systems are now fully compliant for rewind operations and interrogation of the device clock.

10. G-Live

On the Web publication side, some nice enhancements have been made on the athlete summary form. In case of a multiple stages/rounds event the end user can now click on a row of the stage results table to display the whole result details for this stage - split and segment times, laps, track on map,...

Since February 2023, we are proud to offer you a new feature in Wiclax. This feature is available today in beta version for everyone. It will then be invoiced as an option at 100 € excl. tax per year.

This is a feature that we have dreamed of as timekeepers and we hope that it will bring you additional comfort on the finish lines.

In concrete terms, it consists of interrogating a video recorder directly from Wiclax.

Imagine, for example, that a competitor comes to make a complaint because he is not in the ranking. And he tells you that he crossed the finish line just behind number 1665.

All you have to do is find competitor number 1665 in the results grid and right-click to access the Video sub-menu in the contextual menu (note the keyboard shortcut Ctrl+Shift+V).

Immediately, Wiclax will interrogate your video recorder to load the video corresponding to the passage of the runner.

The loaded video shows thirty seconds of recording before and after the passage of the rider concerned. The opening position is approximately 3 seconds before the selected rider passes.

It is possible to stop the video by clicking on the button .

It is possible to scroll the video frame by frame with the right arrow of the keyboard. It is also possible to go backwards with the left arrow, but this is more cumbersome due to the constraints of the video formats. The easiest way to do this is to use the middle cursor to bring the video back to the desired moment.

The button allows you to add a discovered rider to the video directly in Wiclax.

This new feature is based on the use of a video device at the finish line. This video device must consist of a Dahua (one of the leading brands in the sector) digital video recorder and an IP camera.

The validated recorder model for this functionality is the following:
Dahua 4 camera IP recorder

Please note that the firmware of the recorder must be in version 4.

The recorder must be connected to the same local network as the computer hosting the Wiclax software and have an IP address in the same class. Everything can be configured via the interface of the recorder.

On the software side, you will need to install a small add-on module that you can download here: https://wiclax.com/assets/WiclaxVideoLine.exe

Then, you will simply have to set up this information in the video window when you first open it.

It is simply the IP address of your recorder, the channel (it is possible to have up to 4 cameras on these recorders) and the user name and password of your Dahua recorder (you can create a dedicated user).

We look forward to hearing about your use of this feature and will be happy to help you implement it.

Here we go again with this new seasonal delivery, see what's new coming out:

Performances

Was time to make some renewed testing and ground works concerning Wiclax behavior under heavy constraints. Continuous development and integration of new features means also continuous care to provide on these aspects. This time we've focused on mass races configurations, lots of participants and lots of timing locations.

Sparing you complex details about how things are working in the black box, we've eliminated a certain number of bottlenecks and made a better use of parallel task processing. No compromise with Wiclax excellence anyway, with any ranking still computed in real time and ready to be printed/exported/broadcasted. Hoping you'll appreciate the improvements!

Calculated fields

You've already seen them in the custom data section of an event, where you have the ability to enter a calculation formula to feed such a field.

What's new is that we've introduced a few Wiclax specific functions that can be used within formulas:

• TimeToMs(), MsToTime(), AddTimes(), SubTimes(), which can be used to make operations with Wiclax time values.
• WxVar(), which takes as argument any variable identifier as per listed in the custom export format reference that you've maybe already discovered for other purposes. For example among many other possibilities you can obtain the number of finishers in the participant category.

Points calculation

Similarly, we've introduced the ability to edit a custom formula to use for the points calculation. For cases where simple lists of points to award based on place in rankings is not flexible enough.

Bundle reports

Bundle reports are still called Stage summary in Wiclax, cause it's a must have in the context of a cycling stage race. But we aim at giving it a wider purpose like for example when you're requested 2 complementary reports as a single document.

So we continue to refactor a lot of things to bring more flexibility at all levels. Here's a summary of the latest improvements:

• quick selection of reports to embed, each item can be just temporarily disabled
• multiple predefined templates: standard, compact and 2 columns (configurations can be imported/exported and soon to come will be the ability to save a custom list with the event file)
• for each report you can choose a max number of rows, and specify its layout is multi columned
• on the print preview you can click on a sub report and access its own layout options. This includes for example selecting which data fields to print - specifically for this bundle report configuration, choosing a vignette layout, etc...
• at general level you can say the report will start with some cover pages. Combined with the new race communiqués feature, it becomes possible to fill them with some custom graphical content.

Race communiqués

Race communiqués become fully managed with the event: recording of items for each stage, free edition with Word-style formatting and availability for inclusion in a stage summary report. Ideal for cycling races but also to enrich any type of document printed from Wiclax.

Live screens

Continuing with making Live screens design as fun as powerful, 2 great new features:

• some predefined style templates can be applied in one click to result/participant list widgets, sparing you some research on how to tweak CSS style by yourself. Please share your displays if you don't find anything close in this selection, we'll be happy to enrich it.
• access added to the whole list of Google fonts for your screen styling, just pick any from the list.

Prize money

A must have for Criterium like bike races, but not only, a new module delivers this feature.

You can easily setup a new awarding lap during the race, simply entering its prize grid.

For other purposes than prize money, you can also now automatically grant points or time bonuses based on the passing order at a given lap (for races managed as lap races).

Result exchange and/or transfer

Though different scenarios have to be considered and it's not always easy to just have a clear thinking about which operations have to be performed, we've introduced a new dialog aiming at clarifying options when some result data have to be transferred to another participant. Most usual use case is dealing with a bib/chip physical allocation mistake.

Hoping you'll feel more confident with it.

Going along, a new contextual menu Initialize with data from another participant brings the ability to quickly copy registration data under a given bib number. Ideal in case you decide to keep an 'unknown participant' as it comes, with the chip he's wearing, but knowing he was initially registered under a different bib number.

Exporters

We continue to extend possibilities for exports in JSON format - either as local files or as TCP data stream. A data preview now facilitates testing and further processing by external programs.

Arrival graphs

New display mode available to visualize segment times in a stacked view. Makes things easier to spot any eventual anomaly, like a segment obviously too short/long or a missing intermediate time.

Miscellaneous

Result publication: a new publication option allows to activate the display of a 'Provisional ranking' warning banner on the web side.

Lap races: the number of laps to perform for a race can now be modified through a shortcut available from the race statistics & control panel.

Note that we're also introducing here a concept of Active race. This will be important for a context where you have several races or heats defined in the file but only one at a time is going to be competed.

Team data import: to ease some scenarios of participant data processing, a new option provides the ability to merge some independent individual data rows into a single registration in Wiclax. I.e. a single bib, where teammate names will be concatenated.

Real bib numbers: new option for automatic calculation of real bib numbers (those finally appearing on printouts and exports), with addition/subtraction applied to the technical bib. Option available from the race bib numbers setting.

Podiums: in some rare occasions you can be asked to calculate some podiums based on a category set (age groups) which is not exactly the one applied to participants in the file. Now possible with this menu selection:

Conditional formatting: From the contextual menu of a column header (main grids) it's now possible to define formatting rules for the cells, Excel style. For example red+bold if value>xxx.