runningLateWindowInSeconds configuration

[kossavot]

Hi all,

 

while reviewing the OneBusAway server source code, I noticed the runningLateWindowInSeconds parameter in BlockStatusServiceImpl, which defaults to 1800 seconds. From the code comments, it appears this parameter influences how blocks are searched. However, I'm unclear on whether it also impacts arrival and departure predictions when a vehicle is more than 1800 seconds late compared to its schedule.

Specifically, are such late vehicles (> 1800 secs) excluded when querying endpoints like arrivals-and-departures-for-stop?

Also, what is the performance impact of increasing the runningLateWindowInSeconds parameter in the OneBusAway server? Specifically, how does a higher value affect processing time, memory usage, and the overall responsiveness of the system?

Best regards

[Sheldon A. Brown]

Yes, `runningLateWindowInSeconds` will prevent a vehicle-to-block
assignment if the value is exceeded. That means predictions will not
be present for the given block.

As to your performance question, I would suggest benchmarking
(testing) any changes to this setting, as I'm not aware of your
configuration or resources. Increasing this value will increase CPU
and memory usage. It's unlikely this setting alone would cause an
issue, but the only way to be sure is to try it.

Sheldon

> --
> You received this message because you are subscribed to the Google Groups "OneBusAway API" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to onebusaway-ap...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/onebusaway-api/dd834661-90fb-461b-9b47-230d24b9bd44n%40googlegroups.com.

[kossavot]

Thanks for confirming that  Sheldon.

On the same note, can you recall other variables, configurable or not, similar to runningLateWindowInSeconds which can exclude predictions from blocks ?

Thanks

[Sheldon A. Brown]

Searching the codebase for the @ConfigurationParameter would be a good
place to start. From there, you'll need to debug the issue if you are
missing expected data. Starting with the entry point
GtfsRealtimeSource and enabling debug logging of GtfsRealtimeSource
and GtfsTripLibrary is the next step.

Sheldon

> To view this discussion visit https://groups.google.com/d/msgid/onebusaway-api/2d70f115-36a6-4f21-bf5a-e067e39d7290n%40googlegroups.com.

[kossavot]

thank you Sheldon, much appreciated.