Hi @stefan,
I think I might have found a bug in fast regret (for the case where there are both jobs with dependency type INTRA_ROUTE/INTER_ROUTE and jobs with no type in the problem):
Assume in the unassigned job list we have a job A with dependency type INTRA_ROUTE and a job B with no type. When update insertion date, all routes will be updated with the latest version number in the updates map due to job A. However, for job B, only the last modified route will be really updated and added into the insertion data set with the latest version number, and all other routes are not.
Later, when get the best scored job, there is a comparison between the latest version number of the route obtained from the updates map and the version number of the versioned insertion data. Now, for job B, only the version number of the versioned insertion data for the last modified route matches the latest one, and all other routes have out-of-date version number. Therefore, job B can only be inserted into the last modified route or an empty one.
Hopefully I have made myself clear, and do you think this is a bug or do I simply misunderstood something @stefan? Thanks.
Best regards,
He