CI fixes

argoverse · Mar 31, 2023 · 6d9a5c8 · 6d9a5c8
1 parent c9cd2e3
commit 6d9a5c8
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/src/av2/datasets/motion_forecasting/eval/metrics.py b/src/av2/datasets/motion_forecasting/eval/metrics.py
@@ -1,10 +1,10 @@
 # <Copyright 2022, Argo AI, LLC. Released under the MIT license.>
 """Utilities to evaluate motion forecasting predictions and compute metrics."""
 
-import numpy as np
-
 from typing import List
 
+import numpy as np
+
 from av2.utils.typing import NDArrayBool, NDArrayFloat
 
 

diff --git a/tests/unit/datasets/motion_forecasting/eval/test_submission.py b/tests/unit/datasets/motion_forecasting/eval/test_submission.py
@@ -15,13 +15,14 @@
     ChallengeSubmission,
     ScenarioPredictions,
     ScenarioProbabilities,
+    ScenarioTrajectories,
     TrackTrajectories,
 )
 
 # Build valid submission with predictions for a single track in a single scenario
 valid_track_trajectories: TrackTrajectories = np.zeros((2, AV2_SCENARIO_PRED_TIMESTEPS, 2))
 valid_scenario_probabilities: ScenarioProbabilities = np.array([0.6, 0.4])
-valid_scenario_trajectories: ScenarioPredictions = {"valid_track_id": valid_track_trajectories}
+valid_scenario_trajectories: ScenarioTrajectories = {"valid_track_id": valid_track_trajectories}
 valid_submission_predictions = {"valid_scenario_id": (valid_scenario_probabilities, valid_scenario_trajectories)}
 
 # Build invalid track submission with incorrect prediction length