Data Common to all COSIN/io Style Road Types

If the COSIN/io format has been recognized, evrmr looks for the data block $road_type to read the above-mentioned data. These data are used in road profile calculation for all types and in all subsequent invocations:
Name of input variable Unit Meaning
type - A character string consisting of:
  • cleat
  • drum
  • file
  • functionhydropulse_harmonic
  • hydropulse_noise
  • plank
  • pot_hole
  • ramp
  • roof
  • sine
  • sine_sweep
  • spline
  • uneven

Defines the type of the obstacle or irregularity. Normally, for every type, additional parameters are searched for as explained in the Road Profiles and Obstacles in COSIN/io Format section and as follows:
offset mm (Optional) Value to be added after calculation of reference road height (i.e. a shift of the road in a vertical direction).
start_at m (Optional) To minimize irrelevant tire accelerations when momentarily applying a tire deflection, the start of the road profile, as defined by the contents of data block $road_type, can be delayed by the use of a ramp at the beginning of the simulation With parameter start_at the end of this ramp and start of the regular road is defined in terms of travel distance. This delay does not apply to the road types drum and hydropulse. Additionally, several road types have a parameter start that marks the beginning of a single obstacle relative to travel distance 0.
y_min m (Optional) Road height is zero, if .
y_max m (Optional) Road height is zero, if .
t_period s (Optional) Road height is periodic in time, with period interval specified by parameter.
x_period m (Optional) Road height is periodic in the x coordinate, with period length specified by parameter.
y_period m (Optional) Road height is periodic in the y coordinate, with period length specified by parameter.
mu_factor - Friction value factor is used in tire models to modulate friction/stiction coefficients between tread rubber and road surface. If the mu_factor is defined by an arithmetic expression, it may contain x, y, and t as independent variables: . By using this distributed and/or time-dependent, road friction can easily be modeled. The function f may be an arbitrary arithmetic expression as documented in COSIN/io, including 1D and 2D lookup tables, random values, etc.
Depending on the type of road chosen, more data or data blocks are searched for and read, according to the tables in the following sections: