Technician routing and scheduling problem
AnsweredHello,
I am trying to run the code for "Technician routing and scheduling" provided by Gurobi in their Resources Section which is quite similar to one of my projects. In this link (https://gurobi.github.io/modeling-examples/technician_routing_scheduling/technician_routing_scheduling.html) they have provided the results also. But once I run the same code it doesn't give me the same results. Secondly, the kernel of my jupyter notebook remains busy for hours and hours. Although it is giving me results in seconds but the results are not similar.
There is a function named solve_trs0 which makes sure that utilization and time of technician should be printed in the output. But every time I run the code I am not getting these results.My results are shown in the jpeg image attached.
-
Official comment
This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum. Or why not try our AI Gurobot?. -
kindly someone reply this
0 -
Hi Ayesha,
I have just tested this notebook example as well and I do not run into the same issue. Have you made any changes to the code or the input data from the latest version of the notebook found at https://github.com/Gurobi/modeling-examples?
My best guess for debugging, since the Gurobi solve is completed, would be to look at the part of the solve_trs0() function which processes the results. There is a "while True" loop there - this might be stuck in an infinite loop. You could try printing the state of the code on each pass to see why the "break" statement is not being triggered.
0 -
Hello Simon,
thank you for your answer.
I somehow accidentally found the problem. It is not anywhere in coding. Actually, the excel sheet from where data was being read I defined it differently. Hence it was being stuck. Now it is working. Thank you so much for the feedback.
Have a good day
0
Post is closed for comments.
Comments
4 comments