salience | Go package to detect interesting portions of images | Computer Vision library

The right hand side of a Drools rule is regular Java. In Java you can't assign values to a variable before you declare it.

You were really close. You can add the size constraint straight into the HashSet:

Congratulation, you found drools bug DROOLS-6542 - fixed in 7.60.0.Final
There is a workaround - remove mvel dialect for the rule "Invalidate visa application with invalid passport".

BTW, I'd like to propose you drools testing library which may save you great amount of time to mind complicated rules and simplify writing test scenarios. Here is how test may look like.

Yeah, that's a lot of code, but reading the code, and then running it, I can see what's going on.

You're probably getting this error:

The CLIPS Advanced Programming Guide is here: http://clipsrules.sourceforge.net/documentation/v640/apg.pdf

You can use the Load function (section 3.2.2) to load a file. There is an example of its use in section 3.6.1.

You can use the GetNextActivation function (section 12.7.1) to determine if the agenda has any activations.

The simplest way to create facts is using the AssertString function (section 3.3.1). Sections 3.6.2, 4.5.4, and 5.3 have an example use of this function. You can also use the FactBuilder functions described in section 7.1 (with an example in section 7.6.1).

If the results of your program running are represented by facts, you can use the fact query functions via the Eval function to retrieve those values from your program. Section 4.5.4 has an example.

Unless you're using saliences, execution order is non-deterministic. There are no guarantees that Rule A will always go before Rule B. It might always go in this order (A -> B) right now, but that's not guaranteed, and tomorrow or the next time you do a rules change or a version update, it might go in a different order. It usually has to do with the order that rules are loaded into memory, (which is why un-salience'd rules in a single DRL file tend to be executed top of file to bottom of file, because that's the order they're read.)

If your rules are such that you require them to be executed in a specific order, you should put saliences on them so that Rule X will always execute before Rule Y because of the saliences on them. Alternatively, you could rewrite your rules to not rely on execution order (this is considered good practice anyway.)

The only order guarantee that Drools provides is that rules of a given salience will execute at the same time, though the order of those rules within the salience is not guaranteed. Rules with no salience are all defaulted to salience 0, so this guarantee holds true. All of the rules execute, but no order is guaranteed and cannot necessarily be consistently determined ahead of time (hence "non-deterministic.")

So really, at the end of the day, when your question is "which rule gets executed first?" the answer is -- unless you have saliences, it shouldn't matter. And if it does matter, you need to fix your rules.

Assuming that your class definition looks like this:

saliencyMap has values between 0 and 1. You need to rescale the values to 0-255 range. Then, decide if you want otsu threshold or manual threshold. The given value 120 has no effect on Otsu binarization method as itself automatically determines the threshold value.