Hello to all to you!
I am working now quite a while with jsprit and i am questioning myself something, and i want to talk with you about it too.
I think it would be helpfull, if for the unnasigned jobs would me behind some data structure that stores information, why the job isn´t used in the optimization. For example:
Too long distance(20)
So someone can see, that the reason for this job is, that it was in a lot recreation rounds too far away to play(20 times) and also it could not be reached in the given timewindow(4 times).
The problem is, that in own build constrains i can build something like this in. But in the given constraints for timewindows, skills, distance etc i should change the core code. How do you think would this make sence to make an feature issue for that?
My idea would be to to give each job/service a extra structure, for example a list with pairs (Reason, counter). If a reason encounters, and the reason is not in the list it would be added to it. If the reason is already in the list, the counter would be added +1.