Multiple codes for same control
Multiple codes for the same control are separated by dot(s) and any of these codes are equivalent, e.g., finish control with different codes 174 and 175: 112,174.175;101,111. With checked option Normalize multiple controls, 1st control will be used for any control of the group in split times results.
Forking: Code Control Check
Enable [multiple course/forking] to assign several (forked) courses to one class; enter all possible combination. The following example has H17 with 8 combinations and D17/H17K with 2 combinations. Furthermore, the first control and the finish have 2 punching units with different codes.
Forking: Splittimes Output
Chose Options -> HTML output setting -> Splittimes -> Splittimes by ... -> ... to group the output by class, class & course or course.
You can also set a mass start time such that all runners get the same start time regardless when they activated their ECard and adjusting total time and the splittime to the first control. Use the entry Manually and use s as runner/ECard number followed by the the start time (hh:mm:ss:) (e.g., s,19:44:48 or for a give set of classes s;H21;D17;H17-20;H21K;H40,12:04:00,84926,DNF). Note that reading from already deactivated ECards the needed information is lost to calculate the start and finish time.
tTiMe pam (online entry)
Re-use of (old) database for tTiMe pam (online entry)
Open a tTiMe database which is similar to your competition. It's recommend to run first a "Fix & merge double entries" to clean up your database. Then, run the tool "Clean database for upload". If the database has the same classes as your actual competition you can keep the classes.
Logging output window
In oder to log all output (during a competition) you can save the output to a file as HTML. You may also add some comments / remarks to the output window for later use. Note that logging to file does always append to the logging file.
Rename / remap class names
[Tools -> Remap classes renames] a set of class names to one name. Each class name is separated by comma and class name sets are separated by semicolon, e.g., source:D17,DU17;H17,HU17 to destination:D;H.
Excel / OpenOffice import
Control codes for splittimes output
tTiMe does by default not show control codes for splittimes. Check [Options -> HTML output settings -> Splittimes -> Control code] to show control codes. Note that, control codes always will be shown for runners with DSQ or not OK status.
When using different codes for the same control or joker (multiple codes separated by '.') tTime normalized the control codes by picking the first code in the sequence. You can override this by unchecking [Options -> Normalize multiple controls].
Pre-configure tTiMe for server download
Create a short cut and past your presets from your configuration into 'Target', e.g., -server ttime.no
Writing chase start lists
Database editor allows to export chase start lists as HTML/EXCEL with filtering. Note, that the database needs the chase start times, which can be imported.
The course lengths (visible in Eventor) have to be added by hand in the configuration file:
-lengths "<course 1 length in m>,<course 2>,<course 3>,..."
The assignment of course lengths can be verified via then menu item [Database] -> [Check database] :
... L0 : 0 () L1 : 77 (H13-15,H16-18,H19,H40,H60) 2400m L2 : 58 (D13-15,D16-18,D19,D40,D60) 2100m L3 : 21 (DN,HN) 1000m All : 156