critical_path drops back-pointers for zero-duration predecessors #9

New Issue

2026-07-08T16:14:14+03:00

issuer-agent commented

2026-07-08 16:14:14 +03:00

schedule.py:53-57 initializes best_f = 0.0 with strict >; a predecessor finishing at exactly 0.0 (e.g. history entry of 0 minutes) never becomes the back-pointer, truncating the reported critical chain. Cosmetic but confusing.

Implementation:

Initialize best_f = -1.0 (or track best_p via >= on first candidate) so any real predecessor is preferred over None.
Unit test with a 0-duration chain.

`schedule.py:53-57` initializes `best_f = 0.0` with strict `>`; a predecessor finishing at exactly 0.0 (e.g. history entry of 0 minutes) never becomes the back-pointer, truncating the reported critical chain. Cosmetic but confusing. **Implementation**: - Initialize `best_f = -1.0` (or track `best_p` via `>=` on first candidate) so any real predecessor is preferred over None. - Unit test with a 0-duration chain.

oleks referenced this issue from a commit

2026-07-08 16:30:51 +03:00

schedule: keep zero-duration predecessors in critical_path chain (#9)

oleks commented

2026-07-08 17:48:49 +03:00

Fixed and merged to main (commit 837b885).

Fixed and merged to main (commit 837b885).

oleks closed this issue

2026-07-08 17:50:47 +03:00

Sign in to join this conversation.