Use estimated_departure instead of departure in SessionInfo.remaining_time

[Copilot]

Algorithms were inadvertently using actual departure times via SessionInfo.remaining_time, contradicting the design intent that scheduling decisions should be based on estimated/predicted data available in real-world scenarios.

Changes

• SessionInfo.remaining_time now calculates using estimated_departure instead of departure

  # Before
  remaining = min(self.departure - self.arrival, self.departure - self.current_time)
  
  # After  
  remaining = min(self.estimated_departure - self.arrival, self.estimated_departure - self.current_time)

• Test expectations updated to reflect new behavior when estimated_departure ≠ departure

Impact

The remaining_time property is used by preprocessing logic to sort sessions (e.g., by laxity, remaining processing time). This change ensures sorting decisions align with the already-correct behavior in earliest_deadline_first() and least_laxity_first(), which use estimated_departure directly.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>ENH: Algorithms should use estimated_departure instead of departure.</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
Currently algorithms within ACN-Sim use the real departure of the EV. However, this value is not always known perfectly, so instead we should use estimated_departure which can be provided based on real data taken from the user OR predicted in some other way.

Describe the solution you'd like
Replace departure with estimated_departure in ACN-Sim algorithms.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes ENH: Algorithms should use estimated_departure instead of departure. #93

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.