HOME PRODUCT ADD-ONS DEMO SUPPORT NEWS CONTACT  
  PRODUCT  
 
 

rMetrix

rMetrix-A

 

rMetrix 1.8 Release Notes

New features include:

  • In the Accelerometer Data Window, click on the Left Arrow button at the top right of the window. A panel will appear displaying the order of the graphs drawn in the Accelerometer Data Window. Using the mouse, drag any graph row to another row to change the display order of the graph. This feature is useful if one graph waveform has higher amplitudes than another and both still need to be visibly displayed. Click on the Minus button at the top right of the panel to collapse it when ordering is complete.
  • 3 levels of exceptions can now be defined. (In previous versions, only 2 exception levels were available.) Level 1 exception thresholds must be greater than or equal to Level 2 exception thresholds. Level 2 exception thresholds must be greater than or equal to Level 3 exception thresholds. If Level 1, Level 2, and Level 3 all have the same values, only Level 1 exceptions will be displayed throughout the application. If Level 2 and Level 3 have the same values, but Level 1 has a different level, only Level 1 and Level 2 exceptions will be displayed throughout the application. If Level 1, Level 2, and Level 3 all have different values, all three exception levels will be displayed throughout the application.
  • A Toggle Exceptions button has been added to the Graph Toolbar. When toggled on, all exceptions and corresponding threshold lines will be displayed; when toggled off, all exceptions and corresponding threshold lines will not be displayed. This feature is used in conjunction with the settings from the Accelerometer Toolbar. For example, if a performance standard of an accelerometer is toggled off in the Accelerometer Toolbar, and the Toggle Exceptions in the Graph Toolbar has been set to on, those exceptions will not be displayed until the performance standard of the accelerometer is toggled on. This feature does not toggle on/off manual exceptions or notes. To toggle on/off manual exceptions or notes, use the appropriate buttons (Toggle Manual Exceptions, Toggle Notes) in the Accelerometer Toolbar.
  • Speed data for each exception is now uploaded to the rMetrix Enterprise Database for visualization in the online portal.
  • If the Real-Time Database Upload checkbox is checked, the system will keep track of the distance and time travelled based on GPS input by day. The data is stored locally on the computer in C:\ProgramData\dFuzion\rMetrix\gpsdaydatalist.xml and periodically uploaded to the database. Previous days data, once successfully transmitted to the database, will be removed from the local file.
  • Accelerometers can now be mounted in any orthogonal orientation and mapped to the appropriate axis when calibrating the accelerometer in either a New Inspection Setup or Creating Sensor Calibration Data Sets. Mount the accelerometer(s) in the appropriate orientation, then click on Calibrate/Create Sensor Calibration Data Set. After calibration, map each to the appropriate axis (in either the positive or negative directions). Each axis must be accounted for with each sensor; in other words, a sensor must have a mapping to an X (+/-), a Y (+/-), and a Z (+/-). A sensor cannot have two or more axes mapped to the same axis.
  • Email categories have been created to direct exceptions and status messages to the appropriate personnel. The software is configured initially with 3 categories: Status, Inspection Exceptions, and Real-Time Exceptions. Email addresses specified in the Status category are used when sending test messages from rMetrix and rMetrix-A, as well as status messages from rMetrix-A. Email addresses specified in the Inspection Exception category are used in rMetrix after an inspection is completed, by navigating to Inspection->Email Exceptions. Email addresses in the Real-Time Exceptions category can be specified by Level 1, Level 2, and Level 3. Email addresses should be comma-delimited. Users must click Save before switching categories. Users must also click Apply or Save before exiting the Preferences form. Manual Exceptions and Notes are treated as Level 1.
  • Inspection metadata can now be attached to exception emails. A checked box next to the metadata field in Inspection Information will be inserted into exception emails. An unchecked box will not.
  • In Version 1.8, marker preferences have been moved from GIS Point Tools to GIS Tools. Additional marker preferences have been added to allow marker metadata to be added to exception emails. The first new preference is Email Message Fields. Check all the fields that should be included in the exception emails. When an exception occurs, the closest marker is calculated; the email will now include the closest marker's checked email message fields. The fields in this list box are generated from the marker shape file. The actual field name can be edited by clicking on the name in the list box and typing a new name. The second new preference is Email Category. The fields in this list box are also generated from the marker shape file. This preference allows exceptions to be emailed to specific groups based on the selected email category. Once a field is selected, select Preferences->Email->Configure Email Categories. All values from this field will be present with sub-categories of Level 1, Level 2, and Level 3.
  • Inspection notes can now be added to all of the exception list reports: Exception List Report (Field), Exception List Report (Summary) and Exception List Report (Detailed).
  • The FTP settings now check for both availability of the FTP server as well as the existence of the specified FTP path.
  • The GPS engine now supports receiving messages from Beidou and GLONASS satellites.
  • The FFT engine has been updated.
  • Combined profile/alignment geometry exceptions will be displayed as a blue triangle with a green border. The geometry file CSV file type should contain "comb pr/al" for this type of exception.
  • The ISO 2631 reports have been streamlined. The High and Low Frequency settings in the Settings window have been deleted, and the Window setting allows the user to segment a complete analysis area into multiple windows. For example, if the analysis window is 5 minutes long, and this setting is 1 minute, the report will generate the ride comfort values of the entire time period, as well as the ride comfort values of each 1 minute window within the time period. If this setting is 0, the analysis window will not be subdivided and the report will only generate the ride comfort values of the entire time period.
  • A new Sperling Ride Index report has been added, with a Window setting. The Window setting allows the user to segment a complete analysis area into multiple windows. For example, if the analysis window is 5 minutes long, and this setting is 1 minute, the report will generate the ride comfort values of the entire time period, as well as the ride comfort values of each 1 minute window within the time period. If this setting is 0, the analysis window will not be subdivided and the report will only generate the ride comfort values of the entire time period.
  • The System Report and Help->About Box now report the rMetrix System ID as identified in the License file. This System ID is also used in the rMetrix Enterprise Database.
  • Version 1.8 works with NTAD 2015 data. The rMetrix website also uses this information.
  • The accelerometer location list now includes Carbody. If selected, it will map to the ISO 2631 Floor – Sitting location.
  • The Speed Profile Graph now just displays a continuous curve, instead of a curve with white boxes at each data point.

Bug fixes include:

  • In Version 1.7, if the same performance standard was added and deleted multiple times, the corresponding filter file was not removed successfully. This bug has been fixed in Version 1.8.
  • In previous versions of rMetrix, missing accelerometer samples were not handled correctly, thus leading to problems with the CSV export. Missing accelerometer samples are now handled correctly in Version 1.8, and when opening previous inspections with missing samples, the software will correct the graph files so that the CSV export functions works correctly.
  • In Version 1.7, the Jerk and Sliding Measurement analysis reports were missing report titles. This bug has been fixed in Version 1.8.
  • In Version 1.7, creating a calibration data set from the Edit→Accelerometer Calibration Data would occasionally crash. This bug has been fixed in Version 1.8.
  • In Version 1.7, Hot Keys with a number would not register in the Memo field of an exception. This bug has been fixed in Version 1.8.
     


 
 
EMAIL RMETRIX@DFUZION.COM HOME