Skip to content

feat(glides): add revenue field to trip assignment message#17

Merged
rudiejd merged 2 commits into
mainfrom
feat/add-revenue-field-to-glides-vehicle-trip-assignment
Mar 2, 2026
Merged

feat(glides): add revenue field to trip assignment message#17
rudiejd merged 2 commits into
mainfrom
feat/add-revenue-field-to-glides-vehicle-trip-assignment

Conversation

@rudiejd

@rudiejd rudiejd commented Feb 26, 2026

Copy link
Copy Markdown
Member

Asana Ticket: 🔮🐛 Investigate and fix problematic revenue predictions

Adds a revenue field to the VehicleTripAssignment message from Glides. See https://github.com/mbta/glides/pull/3251 for a description of why this field was necessary.

@rudiejd rudiejd requested review from a team, lemald and npatel-mbta and removed request for a team and npatel-mbta March 2, 2026 18:53

@lemald lemald left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't love adding more trip metadata to the vehicle trip assignment messages, but I agree that it's probably the best way to solve the issue at hand for now.

@rudiejd

rudiejd commented Mar 2, 2026

Copy link
Copy Markdown
Member Author

@lemald yeah, this is a "stop the bleeding" type of change in my view as well. Long term, we should implement TODS and share the same concept of revenue and non-revenue trips department wide. If that ever happens, we can trim this field from the trip assignment message.

@rudiejd rudiejd merged commit 80ac5cb into main Mar 2, 2026
1 check passed
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.

2 participants