rMetrix 1.7 Release Notes

New features include:

  • In Version 1.6, once an inspection is uploaded to the database, the exceptions' raw data will not be updated if the user changes the database settings for transmit seconds before, after, or maximum and re-uploads the inspection. In Version 1.7, the raw data will be retransmitted to the database based on the current database settings for transmit seconds before, after, and maximum.
  • File→Open Geometry Defect File has been replaced with the more comprehensive File→Open Data GIS CSV File. This feature will still open traditional TDMS CSV files; however, now users can also open custom CSV files. Similar to the TDMS CSV file, the custom CSV files must also:

    Have a header row with the following three fields: Type, Latitude, and Longitude. Case does not matter.

    Type must contain text listed in the GIS External Layers Config CSV Tag (Located in Edit→Preferences→GIS Tools→Configure External GIS Layers)

    Latitude and longitude must be in decimal degrees.

    Can have additional header fields and data (timestamp, track, id, etc.).

    Must have at least one valid item.

To configure the external GIS features that will be displayed, navigate to Edit->Preferences->GIS Tools->Configure External GIS Layers. Each feature type should have a CSV Tag (the Type identifier in the CSV file), a Layer Name (the name of the GIS Layer displayed in the GPS Data Window), and an image to represent the feature. The recommended image format is 16x16 PNG. Any white color in the image will be displayed as transparent. If a specified image is no longer available on the computer, the configuration for that feature type will be deleted. If a user-defined CSV Tag is the same as a TDMS type, the feature will display as the TDMS type.

  • In accordance with the new Vehicle/Track Interaction Safety Limits of the Track Safety Standards and Passenger Equipment Safety Standards that went into effect on July 11, 2013, a new Performance Standard Threshold Measurement Type of RMS Linear Trend Removed has been added to the software.
  • The Window Toolstrip now has two functions:
    • Select Area For Analysis (Blue Toolstrip Button)
    • Create New Stored Area (Orange Toolstrip Button)

The Window Toolstrip buttons are only available during a previously recorded inspection.

The Blue Toolstrip Button functions the same as the original Window Toolstrip Select Area button in Version 1.6; however, the icon is now colored blue. Click on the Blue Icon, and use the mouse to draw a blue window in either the GPS data window or the Accelerometer Data Window. This data contained within the blue area is used for most Analysis and Report functions.

The Orange Toolstrip Button allows the user to store areas of interest to the hard drive, so that they can be recalled in other inspections. Areas of interest may include track curves or designated track segments of maintenance interest. Click on the Orange Icon, and use the mouse to define the vertices of an orange polygon around the area of interest in the GPS Data Window. Double-click to finalize the area of interest. A prompt will appear allowing the user to name the area of interest. If any of the accelerometer data lies within the area of interest, a corresponding orange window will appear in the Accelerometer Data Window.

A new inspection will display stored areas in the GPS Data Window. The corresponding stored areas in the Accelerometer Data Window will only be displayed at the end of an inspection.

Stored areas can be deleted by right-clicking an orange polygon in the GPS Data Window and using the context menu to delete the stored area (which is referenced by name). If one or more stored areas have the same name, all stored areas with that name in the GPS Data Window and the Accelerometer Data Window will be deleted.

  • Steady State Acceleration Report
    To generate a steady state acceleration report, navigate to the Steady State Acceleration Report menu item in the Reports menu in the main application screen.

    An analysis (blue) window must be selected and/or a stored area must contain inspection data to run this report. Due to the nature of the analysis, it may be necessary to limit the size of the analysis window or select fewer accelerometers for analysis. If your analysis window is too large or there are too many accelerometers selected for analysis, the software will inform you to select a small analysis window or fewer accelerometers. A computer with more memory will be able to analyze larger windows and more accelerometers.

    Individual accelerometers and their raw and/or filtered data can be included/excluded from the report using the Select Accelerometer Data dialog box.

    Each accelerometers' axis' steady state acceleration for each area of interest is listed in tabular format in this section. The following data is provided in the report:

    • Area of Interest Name: Accelerometer/Axis
    • X Mean
    • Y Mean
    • Z Mean
  • Performance Standard Thresholds can be developed based on stored areas (location), as an alternative to time-based thresholds. This can be useful when monitoring track curves or designated track segments of maintenance interest. When designing a performance standard threshold based on stored areas, select the Stored Area radio button in the Performance Standard Threshold window. The options for measurement type are average acceleration and maximum acceleration. To trigger an exception, acceleration data must enter the stored area and exit the stored area (via GPS location), and the average/maximum acceleration must exceed the threshold values in the performance standard. The exception will be placed in location and time at the mid-point of the stored area.
  • Email recipients can be assigned to one or more specific groups to receive certain types of email messages. The email group types are Status, Level 1, and Level 2. If an email address is assigned to the Status group, then status messages will be sent to that email address. (This group only applies to the rMetrix-A product.) If an email address is assigned to Level 1, Level 1 and Manual exceptions will be sent to the email address. If an email address is assigned to Level 2, Level 2 and Manual exceptions will be sent to the email address. If an email address is assigned to Level 1 and Level 2, all exceptions will be sent to the email address. In rMetrix, when selecting Inspection->Email Exceptions, Level 1/Manual exceptions will be emailed to those email addresses assigned to the Level 1 group; Level 2/Manual exceptions will be emailed to those email addresses assigned to the Level 2 group. In rMetrix and rMetrix-A, a test email message (from the Preference window) will be sent to all email addresses, regardless of which groups they are assigned to.
  • The Jerk Analysis displays any stored areas of interest in the windows. In addition, the setting button is available in the analysis. Clicking on this button allows the addition of threshold lines (in g/s, ft/s^3, m/s^3 - depending on unit preferences) at the positive and negative values of the jerk threshold setting. A check box is included to indicate whether or not to display the jerk threshold lines.
  • The Sliding Measurement Analysis has been added. Select a blue window area of interest in either the GPS Data Window or the Accelerometer Data Window. Navigate to Analysis->Sliding Measurement. A form will appear to prompt you to select the Filter Type, Sliding Window Duration (in milliseconds), and the Measurement Type. Select the appropriate values, and click OK. An analysis graph will appear with a sliding value of the measurement type across all of the active axes. Inactive axes can be toggled on.
  • Version 1.7 works with NTAD 2013 data. The rMetrix website also uses this information.
  • If the GPS becomes disconnected during a live inspection, the inspection will continue to record the acceleration data. The software will then automatically try to connect to the GPS at a periodic interval. If the GPS connection is re-established, the GPS data will again be recorded with the acceleration data. If an exception occurs during a period when the GPS is disconnected, the exception will have the last known location data and the fix type will be GPS Disconnected. Exception emails will also denote whether or not the GPS does not have a fix or the GPS is disconnected.

Note: When physically reconnecting certain GPS models, such as the Holux M-1000C, the USB bus will reset and the connection to the accelerometers may be lost. If continuing to record the acceleration data is of utmost importance, do not reconnect the GPS device until the inspection has ended.

  • If an accelerometer becomes disconnected during a live inspection, the inspection will not automatically end. The software will then automatically try to connect to the accelerometer at a periodic interval. If the accelerometer connection is re-established, the accelerometer data will again be recorded.
  • Version 1.7 works with wireless accelerometers. Contact dFuzion for additional information.

Bug fixes include:

  • In Version 1.6, File→Upload Inspection→Database does not consider the user's preferences in the number of seconds before and after the exception of the raw data to transmit. The program will only upload 4 seconds before the exception and 2 seconds after the exception, with a maximum amount of 30 seconds transmitted. The rMetrix.exe.config located in same directory as the rMetrix.exe file can be modified to provide a workaround. This has been fixed in Version 1.7.
  • In Version 1.6, Add Performance Standard did not interpret dual thresholds correctly. It processes dual thresholds as 2 single thresholds. This has been fixed in Version 1.7.
  • In Version 1.6, RMS Mean Removed was calculated incorrectly. This has been fixed in Version 1.7.