You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I can understand the default solver is a combination of backward and foreward scheduling method. The enterprise edition, the ask-reply pattern is stilled based on a backward and foreward method, or it's a totally new method? Due to I don't see it in other resources. If you could also introduce briefly the benefit of that version, that will be great.
Thanks in advance,
Longxing
The text was updated successfully, but these errors were encountered:
The heuristic algorithm in the Enterprise & Cloud Editions is based on the very same ask-reply mechanism. It has some extras compared to the Community Edition (eg to do setup optimization, reschedule existing manufacturing orders to new feasible dates, etc), but it's using the same core.
In addition to the heuristics solver algorithm, the Enterprise & Cloud Editions also have an entirely separate solver. It is designed & optimized for distribution supply chains without manufacturing operations. This solver does not use a ask-reply mechanism.
Thank you for the nice code.
I have a question when I read the docs. It mentions that
FrePPLe comes with a default solver, which implements a heuristic search algorithm. The Enterprise Edition provides a second solver, tailored for distribution-oriented supply chains. When planning a single demand, the algorithm basically consists of a set of recursive functions structured in a ask-reply pattern
So I can understand the default solver is a combination of backward and foreward scheduling method. The enterprise edition, the ask-reply pattern is stilled based on a backward and foreward method, or it's a totally new method? Due to I don't see it in other resources. If you could also introduce briefly the benefit of that version, that will be great.
Thanks in advance,
Longxing
The text was updated successfully, but these errors were encountered: