Package: trajectopy-core
Trajectopy - Trajectory Evaluation in PythonTrajectopy is a toolbox for empirical trajectory evaluation.Key FeaturesTrajectopy offers a range of features, including:Absolute Trajectory Error (ATE) computationRelative Pose Error (RPE) computation with distance- or time-based pose-pair selectionTrajectoryalignmentusing least squares adjustment theory and up to 11 parameters (i.e. similarity transformation, lever arm, time shift)CustomizableHTML reportgeneration (demo) (takes a few seconds to load)Table of ContentsInstallationExemplary EvaluationImporting TrajectoriesProcessing SettingsInstallationCreate virtual environment (Optional but recommended)Unixpython3 -m venv .venvWindowspython -m venv .venvActivate (Unix)source .venv/bin/activateor(Windows).\.venv\Scripts\activateInstallation via pipUpdate pip:pip install --upgrade pipInstall trajectopy:pip install trajectopy-coreOr using the repository:pip install git+https://github.com/gereon-t/trajectopy-core.git@mainExemplary EvaluationThis section shows how to use trajectopy to evaluate two trajectories. The example data can be found in the example_data folder. The full code can be found in the example_scripts folder.Absolute Trajectory Error (ATE)fromtrajectopy_core.pipelinesimportatefromtrajectopy_core.settings.processingimportProcessingSettingsfromtrajectopy_core.trajectoryimportTrajectory# Importgt_traj=Trajectory.from_file("./example_data/KITTI_gt.traj")est_traj=Trajectory.from_file("./example_data/KITTI_ORB.traj")# default settingssettings=ProcessingSettings()ate_result=ate(trajectory_gt=gt_traj,trajectory_est=est_traj,settings=settings)Relative Pose Error (RPE)fromtrajectopy_core.pipelinesimportrpefromtrajectopy_core.settings.processingimportProcessingSettingsfromtrajectopy_core.trajectoryimportTrajectory# Importgt_traj=Trajectory.from_file("./example_data/KITTI_gt.traj")est_traj=Trajectory.from_file("./example_data/KITTI_ORB.traj")# default settingssettings=ProcessingSettings()rpe_result=rpe(trajectory_gt=gt_traj,trajectory_est=est_traj,settings=settings)Importing TrajectoriesTrajectory files must be ASCII files with a csv-like layout. The default column structure that can be read without any configuration is the following:timeposition xposition yposition zquaternion xquaternion yquaternion zquaternion wColumns are expected to be separated by commas by default.It is recommended to provide a header at the beginning of the trajectory file. Header entries always begin with a "#".
Below you can find a table of all allowed header entries and their meaning.HeaderDescription#nameThe name provided here is displayed in plots of the trajectory#epsgEPSG Codeof the datum of the input positions. Required, if geodetic datum transformations are desired. Default: 0, meaning local coordinates without any known geodetic datum#fieldsDescribes the columns of the ASCII trajectory file. Separated with commas.field nameMeaningttimelarc lengths in meterspxposition x / lat (degrees only)pyposition y / lon (degrees only)pzposition zqxquaternion xqyquaternion yqzquaternion zqwquaternion wexeuler angle xeyeuler angle yezeuler angle zvxspeed xvyspeed yvzspeed zExample: "#fields t,px,py,pz" Note: The only column that is allowed to appear multiple times is the "t" column.#delimiterDelimiter used to separate the columns within the file. Default: ","#nframeDefinition of the navigation-frame the orientations of the trajectory refer to. Choices: "enu": East North Up or "ned": North East Down. Default: "enu"#rot_unitUnit of the orientations. Choices: "deg": Degree, "rad": Radians. Default: "rad"#time_formatFormat of the timestamps / dates. Choices: "unix": Unix timestamps (since 01-01-1970), "datetime": Human readable date-times. Default: "unix"#time_offsetOffset in seconds that is applied to the imported timestamps. Default: 0.0#datetime_formatFormat of the datetimes. Only relevant if "time_format" is "datetime". Default: "%Y-%m-%d %H:%M:%S.%f"#datetime_timezoneTime zone of the timestamps. During import, all timestamps are converted to UTC considering the input time zone. Choices:Time zoneor "GPS"#sortingSorting of the input data. Choices: "chrono": Chronologically sorted data (usually the case), "spatial": Spatially sorted data, i.e. along the arc length. Default: "chrono"New since 0.9.2: Experimental ROS bag support for geometry_msgs/msg/PoseStamped messages. Files must have a ".bag" extension. Poses must have positions and orientations. One file can contain multiple trajectories published under different topics.Processing SettingsTrajectopy offers a range of processing options that can be applied to the imported trajectories. These options are:OptionDescriptionAlignmentAlignment of two trajectories using least squares adjustment. The implemented approach can handle a similarity transformation (translation, rotation, scale), a lever arm (3d vector), and a time shift (scalar). Each parameter can be included or exluded from the adjustment depending on the individual sensor modalities using theAlignmentSettings. In addition, preprocessing steps and stochastics can also be configured.MatchingMatching of two trajectories to establish pose-to-pose correspondencies. After matching both trajectories will have the same number of poses. You can choose from different matching methods in theMatchingSettings.ComparisonComparison of two trajectories using absolute (ATE) and relative (RPE) metrics. The relative comparison can be configured using theRelativeComparisonSettings.Alignment SettingsPreprocessing Settingsmin_speed(float): Only poses with a speed above this threshold are considered for alignment.time_start(float): Only poses with a timestamp above this threshold are considered for alignment. The timestamp is given in seconds and is relative to the first common timestamp of both matched trajectories.time_end(float): Only poses with a timestamp below this threshold are considered for alignment. The timestamp is given in seconds and is relative to the first common timestamp of both matched trajectories.Estimation Settingstrans_x(boolean): Enable or disable x-translation of the similarity transformation.trans_y(boolean): Enable or disable y-translation of the similarity transformation.trans_z(boolean): Enable or disable z-translation of the similarity transformation.rot_x(boolean): Enable or disable rotation around the X-axis of the similarity transformation.rot_y(boolean): Enable or disable rotation around the Y-axis of the similarity transformation.rot_z(boolean): Enable or disable rotation around the Z-axis of the similarity transformation.scale(boolean): Enable or disable scaling of the similarity transformation.time_shift(boolean): Enable or disable the estimation of time shift.use_x_speed(boolean): Enable or disable the use of X-axis speed for time shift estimation.use_y_speed(boolean): Enable or disable the use of Y-axis speed for time shift estimation.use_z_speed(boolean): Enable or disable the use of Z-axis speed for time shift estimation.lever_x(boolean): Enable or disable estimation of lever arm in the X-axis.lever_y(boolean): Enable or disable estimation of lever arm in the Y-axis.lever_z(boolean): Enable or disable estimation of lever arm in the Z-axis.sensor_rotation(boolean): Enable or disable estimation of sensor rotation. Independent of the least squares adjustment, a constant rotational offset can be computed between the rotations of both trajectories after the alignment.auto_update(boolean): If set toTrue, the estimation settings are automatically updated and parameters are disabled if they are not significant (experimental).Stochastics Settingsstd_xy_from(float): Standard deviation of XY source position components in meters.std_z_from(float): Standard deviation of Z source position component in meters.std_xy_to(float): Standard deviation of XY target position components in meters.std_z_to(float): Standard deviation of Z target position component in meters.std_roll_pitch(float): Standard deviation of roll and pitch in radians.std_yaw(float): Standard deviation of yaw in radians.std_speed_to(float): Standard deviation of platform speed in (meters per second).error_probability(float): Probability of error used for stochastic testing.Threshold SettingsUsually, these settings can be left at their default values.metric_threshold(float): Iteration threshold for the least squares adjustment regarding the metric parameters.time_threshold(float): Iteration threshold for the least squares adjustment regarding the time shift parameter.Matching Settingsmethod(MatchingMethod): The method used for trajectory matching. Choices:MatchingMethod.NEAREST_SPATIAL,MatchingMethod.NEAREST_TEMPORAL,MatchingMethod.INTERPOLATION,MatchingMethod.NEAREST_SPATIAL_INTERPOLATED. The methods are described below.max_time_diff(float): Maximum allowed time difference when matching two trajectories using their timestamps.max_distance(float): Maximum allowed distance between matched positions during spatial matching.k_nearest(integer): The number of nearest neighbors to consider during spatial interpolation matching.Matching MethodsNearest SpatialThis method matches two trajectories by finding the nearest pose in the target trajectory for each pose in the source trajectory. The distance between two poses is computed using the Euclidean distance between their positions.Nearest TemporalThis method matches two trajectories using their timestamps by finding the nearest timestamp in the target trajectory for each timestamp in the source trajectory.InterpolationThis method matches two trajectories by interpolating the timestamps of one trajectory to the timestamps of the other trajectory. The interpolation is linear for both positions and rotations (SLERP).Nearest Spatial InterpolatedThis method matches both trajectories spatially by requesting the nearest k positions from the reference trajectory for each pose in the test trajectory. Then, an interpolation is performed using a 3d line fit of the k nearest positions. After this operation, both trajectories will have the length of the test trajectory. This method does not support rotation matching.Relative Comparison Settingspair_min_distance(float): Minimum pose pair distance to be considered during RPE (Relative Pose Error) computation.pair_max_distance(float): Maximum pose pair distance to be considered during RPE computation.pair_distance_step(float): Step in which the pose pair distance increases.pair_distance_unit(Unit): Unit of the pose pair distance. Choices:Unit.METER,Unit.SECOND.use_all_pose_pairs(boolean): If enabled, overlapping pose pairs will be used for relative metrics calculation.RPE BackgroundFor this metric, relative pose-pair differences are compared. The distance between two poses can be specified by the user and can be either time- or distance-based. The comparison involves finding pose pairs separated by a specific distance or time interval, computing the relative translation and rotation between the reference and estimated pose pairs, and calculating the translational and rotational difference normalized by the distance or time that separated the poses.Find pose pair separated by e.g. 100 m in reference trajectory. This pair represents the start and end poses of a sequence of size $N$.Find the corresponding pose pair in estimated trajectoryCompute relative translation and rotation between the reference pose pair$\Delta_{P~ref} = P_{ref, 1}^{-1} \cdot P_{ref, N}$Compute relative translation and rotation between the estimated pose pair$\Delta_{P~est} = P_{est, 1}^{-1} \cdot P_{est, N}$Compute transformation between 3) and 4)Compute translation and rotation error from 5)Divide 6) by the distance or the time that separated both poses (e.g. 100 m).This metric does not require both trajectories to be aligned. Units are m/m: %, deg/m for distance based comparison and m/s, deg/s for time-based comparison.Example:Minimum pose distance: 100Maximum pose distance: 800Distance step: 100Distance unit: MeterResults in pose distances: [100 m, 200 m, 300 m, 400 m, 500 m, 600 m, 700 m, 800 m]Furthermore, the user can choose to either use consecutive pose pairs (non-overlapping) or all posible pairs (overlapping).Report SettingsVisualization Settingsscatter_max_std(float): The upper colorbar limit is set to the mean plus this value times the standard deviation of the data. This is useful to prevent outliers from dominating the colorbar. Default value is 4.0.ate_unit_is_mm(bool): Indicates whether the unit of Absolute Trajectory Error (ATE) is millimeters. Default value is False.directed_ate(bool): Indicates whether the ATE is split into along-, horizontal-cross- and vertical-cross-track direction. Default value is True.histogram_opacity(float): The opacity of the histogram bars. Default value is 0.7.histogram_bargap(float): The gap between histogram bars. Default value is 0.1.histogram_barmode(str): The mode of displaying histogram bars. Default value is "overlay".histogram_yaxis_title(str): The title of the y-axis in the histogram. Default value is "Count".plot_mode(str): The mode of displaying plots. Default value is "lines+markers".scatter_mode(str): The mode of displaying scatter plots. Default value is "markers".scatter_colorscale(str): The colorscale for scatter plots. Default value is "RdYlBu_r".scatter_axis_order(str): The order of the axes in scatter plots. Default value is "xy". If 3d plotting is desired, also specify "z".scatter_marker_size(int): The size of markers in scatter plots. Default value is 5.scatter_detailed(bool): Indicates whether to show scatter plots for each degree of freedom. Default value is False.Mapbox SettingsThese settings currently only apply to trajectory only plots without deviations.scatter_mapbox(bool): Indicates whether the trajectory should be plotted onto a map. Default value is False.scatter_mapbox_style(str): The style of the map. For some styles, a Mapbox token is required. Default value is "open-street-map".scatter_mapbox_zoom(int): The zoom level of the map. Default value is 15.scatter_mapbox_token(str): The Mapbox token. Default value is "".The mapbox token can be obtained fromhttps://www.mapbox.com/after creating a free account.Position Units and Namespos_x_name(string): Name for the X-axis position. Default: "x".pos_y_name(string): Name for the Y-axis position. Default: "y".pos_z_name(string): Name for the Z-axis position. Default: "z".pos_x_unit(string): Unit for the X-axis position, Default: "m".pos_y_unit(string): Unit for the Y-axis position, Default: "m".pos_z_unit(string): Unit for the Z-axis position, Default: "m".pos_dir_dev_x_name(string): Name for the directed position deviation in along-track direction. Default: "along".pos_dir_dev_y_name(string): Name for the directed position deviation in horizontal cross-track direction. Default: "cross-h".pos_dir_dev_z_name(string): Name for the directed position deviation in vertical cross-track direction. Default: "cross-v".Rotation Units and Namesrot_x_name(string): Name for the roll rotation. Default: "roll".rot_y_name(string): Name for the pitch rotation. Default: "pitch".rot_z_name(string): Name for the yaw rotation. Default: "yaw".rot_unit(string): Unit symbol for rotation. Default: "°".Export Settingssingle_plot_export(ExportSettings): The export settings for single plots. Default value is an instance of ExportSettings with width=800 and height=450.two_subplots_export(ExportSettings): The export settings for two subplots. Default value is an instance of ExportSettings with width=800 and height=540.three_subplots_export(ExportSettings): The export settings for three subplots. Default value is an instance of ExportSettings with width=800 and height=750.single_plot_height(int): The height of a single plot. Default value is 450.two_subplots_height(int): The height of two subplots. Default value is 540.three_subplots_height(int): The height of three subplots. Default value is 750.Export Settingsformat(string): The export format. Choices: "png", "svg", "jpeg", "webp". Default: "png".height(integer): The export height in pixels. Default: 500.width(integer): The export width in pixels. Default: 800.scale(integer): The export scale. Default: 6.