Analyzer: Add time-filtering functionality #128
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new time-filtering functionality for analyzing link and vehicle data over a specified time window (
t_seconds
). This allows for more granular, time-sensitive analysis, which is particularly useful when evaluating the most recent simulation behavior. It basically allows inputtingt_seconds
intovehicles_to_pandas
,link_to_pandas
andarea_to_pandas
, which makes it collect the lastt_seconds
of simulation time.It's a clean implementation of PR #123 and is part of issue #120.
A few things to note:
t_seconds
API is maybe still not ideal. Maybe you want to either:t_start
andt_end
, and collect between that period.t_bin
, and then slice up the data in equal parts of that width.Things to review:
or t_seconds is not None
to theif s.flag_pandas_convert == 0 or t_seconds is not None:
check invehicles_to_pandas
. Might be more elegant ways to solve it.This branch can be installed with: