Re: [rules-users] Fwd: Retrieving constraints based on a manual solution

Hello Sreeni, This is what I interpret from your question: 1. you have some sort of working solution that is manually optimized to some degree (by human?); 2. you are willing to determine what constraints are still violated based on a rule base you created with drools but WITHOUT changing the actual manual working solution and WITHOUT running solver for multiple times; If this interpretation is correct, there is a way in drools planner to calculate score once and iterate working memory looking for constraint occurrences. WARNING, this API is intended to be internal and thus subject to a likely change: ScoreDirector scoreDirector = solver.getScoreDirectorFactory().buildScoreDirector(); scoreDirector.setWorkingSolution(schedule); scoreDirector.calculateScore(); <- only once, causes working memory to fire all rules but does not involve solver "search loop" WorkingMemory workingMemory = ((DroolsScoreDirector) scoreDirector).getWorkingMemory(); Iterator<ConstraintOccurrence> it = (Iterator<ConstraintOccurrence>) workingMemory .iterateObjects(new ClassObjectFilter(ConstraintOccurrence.class)); while (it.hasNext()) { //here you collect constraint occurrences and prepare your report } Hope this helps, for a complete example of the usage of this (internal!) api see drools planner examples from Geoffrey on Git. br Reinis On 01/07/2013 04:38 AM, Sreeni Maheshwaram wrote: