Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sorting Jobs #59

Open
ozansabirlioglu opened this issue Aug 16, 2018 · 3 comments
Open

Sorting Jobs #59

ozansabirlioglu opened this issue Aug 16, 2018 · 3 comments

Comments

@ozansabirlioglu
Copy link

Hi Tim,

Can i ask a question about dispatching jobs? I created process route, production resources etc. But when
code is scheduling, which parameters is minimizing? How can we manage scheduling parameters?

Thank you.

@timnon
Copy link
Owner

timnon commented Aug 18, 2018

Please be more specific with the question

@ozansabirlioglu
Copy link
Author

Thank you for quick feedback Tim. 👍

i defined process route (tasks), resources etc. Then, i solve problem with using "solvers.mip.solve". After that i get a schedule. But i dont know what is objective function?

For example, i am scheduling production machines. sometimes i want to minimize total setup time, sometimes i want to minimize late order number. how can I solve for like purposes?

@timnon
Copy link
Owner

timnon commented Sep 23, 2018

The way to set objectives is currently quite limited. The default objective is to minimize the sum of starting times of tasks. But you can heuristically optimize by changing parameters to see until when a feasible solution can be found.

So if you want to minimize total setup times, and setups are tasks, you can search for the minimum number of required setups. Actually, for this case, you can also set a parameter called schedule_cost to specify the cost of scheduling of some task.

Hence, it is usually possible to approximate an objective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants