Adding runs to the database
When the current session of analysis is completed and the program is shut down, it automatically checks to see if all the currently loaded run files are already included in the database. If they are not stored in the database already, then the user is given the opportunity to add them in:
If “Yes” is selected, then the user is prompted for information about the run:
Most of this information is taken from whatever has been set in the run manager. If no information was set in the run manager then some fields will either be shown as blank, or “NA” (not available)
All fields can be edited as required. Note that since the run files can be sorted by Driver/Location/Vehicle is best to make only add in new ones if there isn’t already a suitable definition. For example if “Elise” already exists in the data base, then avoid adding duplicates like “Lotus Elise” or “Tony’s Elise” or “elise” as these will case the runs to be treated as if they were different cars.
Once okay is selected, then the run will be copied over to the database directory. For most run files this typically only takes a few seconds. However, if the run also has a video file associated with it then it can take significantly longer. Clicking cancel will result in the saving to database being aborted.
Note that if the run is already stored in the database, then instead of being prompted to see if you wish to add it to the database, the user is prompted to see if you wish to update the database:
If you select yes then the run file, the configuration files and any settings are updated.
IMPORTANT: the databasing system checks to see if it’s a “new run” by scanning it’s data and generating a “checksum” for each file. This means that is the run file is altered in any way then it will be treated as a new file. Normally this is desireable behaviour, however sometimes it can be inconvenient. For example if you load a run from the database, trim off some of the data from the start (even just stationary data whilst in the pits) then this will mean you have 2 runs which contain the same data, one untrimmed and one trimmed. The only work around this case is to delete the original untrimmed run from the database.