There is currently no error generated when a score evaluation returns NaN - this can lead to hidden errors. Best to add a trap, like: ``` if (!Parameters.checkFinite(score)) throw new ArithmeticException("Failure to evaluate score for XXX"); ```
There is currently no error generated when a score evaluation returns NaN - this can lead to hidden errors. Best to add a trap, like: