Traffic Peak Period Detection from an Image Processing View
Bibliographic record
Abstract
Traffic peak period detection is very important for the guidance and control of traffic flow. Most common methods for traffic peak period detection are based on data analysis. They have achieved good performance. However, the detection processes are not intuitional enough. Besides that, the accuracy of these methods needs to be improved further. From an image processing view, we introduce a concept in corner detection, sharpness, to detect the traffic peak periods in this paper. The proposed method takes the traffic peak period detection problem as a salient point detection problem and uses the image processing strategies to solve this problem. Firstly, it generates a speed curve image with the speed data. With this image, the method for detection of salient points is adopted to obtain the peak point candidates. If one candidate has the lowest speed value, this candidate is the peak point. Finally, the peak period is gotten by moving forward and backward the corresponding time of the peak point with a time interval. Experimental results show that the proposed method has achieved higher accuracy. More importantly, as the proposed method solves the traffic peak period detection problem from an image processing view, it has more intuition.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".