An acceptable solution is good enough for the requirements and use case, even when it is not the optimal solution. Whether “good enough” works depends on the consequences of being imperfect. section 4.2
Judge acceptability by considering:
- Requirements: the candidate must satisfy the problem’s constraints. section 4.2
- Fitness: a higher-value answer may be preferable even when finding it takes time. section 4.2
- Use case: a good-enough recommendation may be fine, while a mission-critical health system may require more certainty. section 4.2
Choosing items for a knapsack
A knapsack must stay within a weight limit while maximizing item value. With many items, checking every combination becomes expensive, so an evolutionary algorithm may return a high-value combination without guaranteeing the single best one. That combination is acceptable if it meets the use case’s requirements. section 4.2
