Skip to content

Renamed telemetry -> trajectory - #58

Merged
RomanPszonka merged 4 commits into
mainfrom
rename-telemetry-trajectory
Nov 29, 2025
Merged

Renamed telemetry -> trajectory#58
RomanPszonka merged 4 commits into
mainfrom
rename-telemetry-trajectory

Conversation

@hrishiballal

Copy link
Copy Markdown
Contributor

This PR updates the file names from telemetry which is incorrect naming for files to trajectory

@hrishiballal

Copy link
Copy Markdown
Contributor Author

It also makes some minor changes to the scenario files

@RomanPszonka RomanPszonka left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hrishiballal tests are failing because of name mismatch - need to make sure all places are renamed

@atti92

atti92 commented Nov 29, 2025

Copy link
Copy Markdown
Contributor

Shouldn't we also rename the config from "telemetry:"?

@hrishiballal

Copy link
Copy Markdown
Contributor Author

Yes, trajectory is provided in the files (GeoJSON) and telemetry is generated from that trajectory file (per the ASTM standard data definitions)

@hrishiballal

Copy link
Copy Markdown
Contributor Author

@atti92 , @RomanPszonka , is the integration test failure by design?

Comment thread config/default.yaml Outdated
comment out broken scenario
@RomanPszonka
RomanPszonka merged commit 7e89011 into main Nov 29, 2025
2 checks passed
@RomanPszonka
RomanPszonka deleted the rename-telemetry-trajectory branch November 29, 2025 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants