330 likes | 336 Views
A systematic approach to identify calibration issues in WIM systems through statistical analysis and simulated scenarios. Overcome limitations and improve reliability of WIM data.
E N D
Implementation of WIM Data Analysis and Simulated Scenarios 12/15/2014
Objective • Limitations of current practice • Fails to identify the time point when WIM system went out of calibration • Reliability of WIM data is questionable • Limited resources to perform frequent on-site calibration checks • Goal • Systematic approach to identify time point when WIM system went out of calibration • Estimate the bias in WIM sensor
EM Fitting of a 3-Component Mixture Model WIM station #37, lane 1, on 05/15/2012
WIM# 37 Lane 1, Vehicle Class 9 EM Estimated Daily Average Fully Loaded GVW
Statistical Process Control Technique • Original CUSUM Approach (Page, 1954) • Decision based Interval (DI) CUSUM(Hawkins,1998) • Upper CUSUM • Lower CUSUM
DI based CUSUM • Upward shift: • Downward shift: • Algorithm parameters: decision interval reference value • Choice of h & k: false positive tolerance
Limitations • Independent assumption • Autocorrelation function (ACF) plot from station# 29 • Presence of autocorrelation results in higher number of false alarms.
WIM Sensor Drift Analysis: Case Study • Data from station#29, Lane 1 Average daily EM estimates of fully loaded class 9 vehicles • Data partitioned into 2 subsets: • Learning Set • Testing Set
Fitting Learning Sample AR(1) Model: where, ~N(0,) Estimated Parameters:
Prediction on Testing Sample AR(1) Residuals: Upward CUSUM on standardized residuals: Estimate of shift in Mean level:
Prediction on Testing Sample AR(1) Residuals: Upward CUSUM on standardized residuals: Estimate of shift in Mean level:
CUSUM based DI Estimated shift, =5.3 kips (6% of average daily GVW) Time of the shift: 05/10/2011 Validation: MnDOT’s test run on 06/08/2011: shift by 6 kips
Software Implementation • Windows 7 & .NET framework 4 • Microsoft .NET based application • Integrated with R statistical software through R.NET control (open source)
Flowchart of Data Analyst Software 1. EM Analysis EM Analysis Set Path Select Station, Lane, Year, Month Load GVW9 Data Process EM Output EM Data to File EM Files CalibrationFiles 2. CUSUM Analysis Select Station, Lane, Date Period Load Calibration Log File Set Path Load Processed EM Data CUSUM Analysis Model Testing Sample Model Learning Sample CUSUM Analysis Estimate Sensor Drift Result Output
Instability in WIM Data Final calibration: 5%
Instability in WIM Data Final calibration change= 3% Final calibration change= - 4%
Simulated Scenario #1 Sensor Shift ( =5 kips T= 150; Learning Sample, Tl =60 Stationarity test: Data is covariance-stationary
Splitting the Testing Sample Data is splitted into 30 days (T1=30) Output from R: No upward shift found in WIM sensor No downward shift found in WIM sensor
2nd part of Testing Sample Output from R: No upward shift found in WIM sensor WIM sensor shifted by -3.94 kips (~5%) on 93
Consistency of WIM Sensor Shift Updated Mean level: Output from R: WIM sensor bias of -3.94 kips (~5%) at index# 93 is consistent
Simulated Scenario #2 T= 150; Learning Sample, Tl =60 Stationarity test: Data is covariance-stationary
Splitting the Testing Sample Output from R: No upward shift found in WIM sensor No downward shift found in WIM sensor Data is splitted into 30 days (T1=30)
2nd part of Testing Sample Output from R: No upward shift found in WIM sensor WIM sensor shifted by -3.79 (kips) at index= 93
Consistency of WIM Sensor Shift Updated Mean level: Output from R: Warning message: Estimated WIM sensor bias is not consistent
Next Step • Implementation stage • Incorporate the WIM sensor bias consistency check • Test WIM analysis for new data • Task 6 – Adjust WIM data • Task 7 – Draft final report & user manual • Task 8 – Final report