...
- When a new logger comes online, it won't start generating occupation events for at least a day.
- Track Circuit flicks will count as an occupation event because there is no minimum time or number of events required for an occupied region.
- If a misconfigured asset is fixed, it will take up to a week for sensible occupation events to be found. This is because the typical threshold value per asset is reset after a week.
- If non track circuit data is assigned to a track circuit asset, the results will likely be garbage.
- If the last days worth of data is nonsense for some reason or contains zero occupations, this will result in typical min and max values which are very similar. This could result in the algorithm trying to classify noise in the clear zone as occupations. This could create a huge number of nonsense occupations. Therefore, system admins have the ability to turn
- Channel associated to a track asset mid occupation - first occupation will be missed?
- If no event is received between the last clear event and the start of the occupation, the occupation will not have a nice pre-occupation clear region.
- In the future, Track circuit data coming in too frequently or garbage occupation events (e.g. nonsense channel / misconfigured logger) can be automatically blocked. At the moment however, it requires manual intervention to disable the feature for an asset.
The 24 hour cache is based on real time not event time!
Flow Chart
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|