[benchmarker] Add active flight operation - #1669
Open
BenjaminPelletier wants to merge 3 commits into
Open
Conversation
BenjaminPelletier
marked this pull request as ready for review
August 26, 2026 17:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
benchmarker's primary unit of interest is an "operation". These are often queries (e.g., createOperationalIntent), but sometimes other operations of interest, like a "flight" which is defined to cover all management aspects of the flight such as UTM operations like creating the operational intent. When attempting to understand the timeline, a useful operation would be the time the virtual operator is actually using the airspace (start of volumes until actual end of flight). This PR adds that operation.
By default, this operation extends from the beginning of the first volume until the actual end of the operation as indicated by the operator (usually prior to the end of the last volume). But, slow UTM activities can push the start forward (e.g., if operational intent activation overruns past the start time). Success of this active flight operation depends on whether all preflight clearances were obtained successfully (including obtaining these clearances by the start time of the volumes, if timely clearance is required).
An example timeline looks as below; the active flight blocks are the lighter, smaller blue blocks.