Skip to content

Conversation

@rtpg
Copy link
Collaborator

@rtpg rtpg commented Nov 12, 2025

Unfortunately I haven't added tests for this one just yet, but have added tests that use this to a private repository that validate that this is working.

When enabled in the plan configuration, this makes sure that departures must happen within a place's times, not just arrivals. This is especially important when dealing with breaks, because the departure there can be affected by a mid-job break.

With strict departure provided to the Problem, departures must not go
beyond the provided place time windows (the existing behavior only
limits arrival time)
route_ctx.route(),
activity_ctx.target,
activity_ctx.target.schedule.arrival,
);
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

the core logic (we can't use self.activity.schedule.departure directly because that departure might be dynamically updated through break's activity cost...)

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