rMetrix 1.6 Release Notes

New features include:

  • The Exception Data Window, the GPS Status Bar, and inspection emails include heading information for exceptions.
  • Inspection emails contain marker (milepost) information.
  • The inspection metadata file stores the X, Y, and Z calibration values for each accelerometer.
  • The user can define the Accelerometer Data Window's minimum and maximum acceleration values for the graph using Edit→Preferences→Graph.
  • The GPS Data Window status bar now displays the GPS location in decimal degrees instead of degrees, minutes and seconds.
  • The GIS toolstrip includes a button for toggling on/off GIS layers.
  • The user can open a geometry defect file for display in the GPS Data Window. This feature works with data exported from the ATIP Track Data Management System, as well as your own custom data sets. Navigate to File→Open Geometry Defect File to open the geometry defect file. Navigate to File→Close <Geometry Defect Filename> to close the geometry defect file. The geometry defect file:
    • Must be in CSV format.
    • Must have a header row with the following three fields: Type, Latitude, and Longitude. Case does not matter.
    • Type must contain the text listed in the Type column in the table below. Case does not matter. For example, a defect with type “R Prof 31” will be identified as a profile geometry defect.
    • Latitude and longitude must be in decimal degrees.
    • Can have additional header fields and data (timestamp, track, id, etc.).
    • Must have at least one defect listed in the table below.
    • The table listed below presents the geometry defects that will be visualized in rMetrix. When the user left-clicks on one of these symbols in the GPS Data Window with a mouse, a text box will appear in the top right of the GPS Data Window with all of the other information about the defect in the CSV file (i.e., timestamp, track, id, etc.).

    Geometry Defect



    Wide Gage

    gage wide

    Narrow Gage

    gage narrow

    Gage Change

    gage change

    Cross Level

    rev elevation
    unbal elev






    rail impact







    Limited Speed

    lmt speed

    Carbody Vertical (Ride Quality)


    Carbody Lateral (Ride Quality)


    Truck Vertical (Ride Quality)


    Truck Lateral (Ride Quality)


  • The user can run the raw data through different performance standard engines to perform “what-if” scenarios. Navigate to Analysis→Add Performance Standard. The user can also use Analysis→Delete Performance Standard to remove different performance standards from the inspection, including the inspection’s original performance standard.
  • The location of uploading inspections via FTP has changed in version 1.6. The user can upload inspections via FTP by navigating to File→Upload Inspection→FTP.
  • If you are an active RAMP subscriber, exceptions can be uploaded to a central database for access via a secure website. Database settings are entered in Edit→Preferences→Database. dFuzion will provide these settings to active RAMP subscribers.
    • Method 1 – Real-time Inspection Exception Database Upload
      • If the database settings are set, and there is an active WiFi connection on the rMetrix computer, exceptions will be uploaded to the database every minute.
      • If exceptions are not transmitted to the database due to network disruptions during its original inspection, the exceptions will be transmitted to the database the next time a new inspection is started and a valid connection to the database can be made.
      • If the database settings are empty, exceptions will not be uploaded to any database, and they will not spool for future transmission to the database.
    • Method 2 – Post-Inspection Exception Database Upload
      • If the database settings are set and valid, and there is an active WiFi connection on the rMetrix computer, exceptions from existing inspections can be uploaded to the database by navigating to File→Upload Inspection→Database. This function is only available when there is no inspection loaded or in progress. Exceptions already in the database will not be duplicated.
      • If the inspection was recorded in a previous version of rMetrix (1.5 or earlier), the Inspection Metadata File will have to manually edited by the user to upload the exceptions to the database. The System Name and Model fields will have to be added to the inspection metadata file. See the picture below as an example. Please contact dFuzion, Inc. for the information that should go into these fields.

  • The user can perform jerk analysis on an inspection’s raw acceleration data. After loading the inspection, select a window of data to analyze and then navigate to Analysis→Jerk.
  • The user can navigate to Edit→Preferences→Graph and select the units of acceleration: g, Metric (m/s^2), or Imperial (ft/s^2). The acceleration units propagate through to the Accelerometer Data Window, the Exception Data Window, Analysis functions, and Report functions.
  • The Accelerometer Data Window now displays GPS speed data by default. The GPS speed data can be visually toggled on and off by clicking the Toggle Speed button in the Graph Toolbar. Navigate to Edit→Preferences→Graph to specify the Y range of speed (minimum and maximum). The units of speed are dictated by the Units in Edit→Preferences→General, not Edit→Preferences→Graph. The color of the graph changes based on whether or not there is a fix at the time the speed was reported from the GPS. The user can set these colors (speed with fix and speed with no fix) in Edit→Preferences→Graph.
  • The Speed Profile report displays the speed graph in two different colors, speed with fix and speed with no fix. The user can set these colors in Edit→Preferences→Graph.
  • Performance Standards can now be designed with dual, simultaneous thresholds. In previous versions, a performance standard consisted of a variable number of thresholds, each of which could trigger exceptions. In this latest version, a performance standard still consists of a variable number of thresholds; however, two of those thresholds can be analyzed simultaneously to trigger an exception together. Both of these thresholds must have the same window size; however, measurement type, exclude duration, axis, level 1 threshold and level 2 threshold values can be independent. If two thresholds are analyzed simultaneously, they will not be analyzed individually.
  • The software displays date and time fields according to the current localization of the computer.

Bug fixes include:

  • In Version 1.5, if all three graph panes (x, y, and z) were toggled off and the graph source (raw, filtered) was changed, the program would error. This bug is fixed in Version 1.6.
  • In Version 1.5, if an exception occurred right before an email was delivered, that exception may not have been delivered via email. This bug is fixed in Version 1.6.
  • In Version 1.5, if a new performance standard is being created, and only one threshold is created, that threshold cannot be deleted without causing a crash. This bug is fixed in Version 1.6.
  • In Version 1.5, the Speed Profile Analysis would not display level 2 exceptions with the correct border (accelerometer) color. This bug is fixed in Version 1.6.
  • In Version 1.5, the Exception Distribution Analysis would not display level 2 exceptions with the correct interior (level 2) color; all level 2 exceptions were displayed as level 1 exceptions. This bug is fixed in Version 1.6.
  • In Version 1.5, the rMetrix user interface would display unorthodox colors if the Windows Classic theme was selected. This bug is fixed in Version 1.6.
  • In Version 1.5, the Metadata Template Editor did not display the up and down arrows correctly on some computers. This bug is fixed in Version 1.6.