Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G-factor Speed Calculation Model QC #420

Open
thehanggit opened this issue Oct 9, 2024 · 2 comments · May be fixed by #482
Open

G-factor Speed Calculation Model QC #420

thehanggit opened this issue Oct 9, 2024 · 2 comments · May be fixed by #482
Assignees
Labels
unplanned Unplanned work added to current sprint, after sprint planning

Comments

@thehanggit
Copy link
Contributor

This issue follows on #386 to check generated speed data quality for the clearinghouse model int_clearninghouse__detector_g_factor_based_speed.

The goal is to ensure that the developed speed algorithm aligns with the current PeMS system to some extent.

@thehanggit thehanggit added this to the Data Quality Checks milestone Oct 9, 2024
@jkarpen jkarpen added the unplanned Unplanned work added to current sprint, after sprint planning label Oct 17, 2024
@thehanggit
Copy link
Contributor Author

The hourly average speed performance comparison between my output and current PeMS system on GP lane is shown below. (HOV lane data is sparse) The findings are listed below

  1. The speed calculation is purely based on normalized flow values volume_sum and occupancy_avg. If there is no data for the two columns, speed would consider as null. I assume if the detector is not working, there will be no values for both. In that case, would it be more accurate than using detector status as Boolean values to filter out the data?
  2. Overall, it is more diverse with relatively high variance than the current PeMS's speed. Not too worry about this difference since PeMS speed is post-processed. We will continue speed QC after smoothing through the imputation model.
  3. For each lane, I set up an upper bound to avoid outliers as PeMS did after diving into their datasets. We can talk about this settings to determine whether it should be included in this model or not.
  4. The average speed for lane 3-6 is slightly higher than PeMS speed. Not sure what happened and may need your feedbacks.

Daily Average Speed for Each GP Lane PeMS Modernization
Daily Average Speed for Each GP Lane

@jkarpen
Copy link

jkarpen commented Oct 24, 2024

Next steps on this: @thehanggit to do additional analysis/comparisons, but waiting on comparison data to be brought over from the old PeMS system. Per @pingpingxiu-DOT-ca-gov that data should come early next week.

@jkarpen jkarpen linked a pull request Nov 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unplanned Unplanned work added to current sprint, after sprint planning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants