You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: monitoring/uss_qualifier/scenarios/astm/utm/flight_intent_validation/flight_intent_validation.md
-17Lines changed: 0 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,6 @@ FlightIntentsResource that provides the following flight intents:
21
21
-`invalid_activated_offnominal`: state mutation `Activated`
22
22
-`invalid_too_far_away`: reference time mutation: reference time pulled back so that it is like the operational intent is attempted to be planned more than OiMaxPlanHorizon = 30 days ahead of time
23
23
-`valid_conflict_tiny_overlap`: volumes mutation: has a volume that overlaps with `valid_op_intent` just above IntersectionMinimumPrecision = 1cm in a way that must result as a conflict
24
-
-`invalid_too_many_vertices`: volumes mutation: has more than OiMaxVertices = 10000 vertices in total across its volumes
25
24
26
25
### tested_uss
27
26
FlightPlannerResource that will be tested for its validation of operational intents.
@@ -49,22 +48,6 @@ The tested USS is requested to remove all flights from the area under test.
49
48
50
49
51
50
## Attempt to plan invalid flight intents test case
52
-
### Attempt to plan flight with too many vertices in its volumes test step
53
-
The user flight intent that the test driver attempts to plan has too many vertices across its volumes, more than
54
-
OiMaxVertices = 10000 vertices. As such, the planning attempt should be rejected.
55
-
56
-
TODO: add check that intent was not planned at DSS
57
-
58
-
#### Incorrectly planned check
59
-
If the USS successfully plans the flight or otherwise fails to indicate a rejection, it means that it failed to validate
60
-
the intent provided. Therefore, this check will fail if the USS indicates success in creating the flight from the user
61
-
flight intent, per **[astm.f3548.v21.OPIN0020](../../../../requirements/astm/f3548/v21.md)**.
62
-
63
-
#### Failure check
64
-
All flight intent data provided was complete and correct. It should have been processed successfully, allowing the USS
65
-
to reject or accept the flight. If the USS indicates that the injection attempt failed, this check will fail per
0 commit comments