i've just realized there's a potential bug in expert lotto when the filters/stats are multithreaded: if you use a filter or calculate stats that adjust segment sizes to values different from the default ones then there's a high risk that those filters/stats will perform incorrectly. it's due to the fact that a filter running in one thread may adjust segment sizes to some values and another filter running in other thread may adjust segment sizes to different value thus clashing with each other.
i'll fix this in the next build however it will be an incompatible API change so some of your plugins may stop working. naturally, i'll fix all of my plugins but joe (i hope he's reading this:) will have to change his plugins that are based on wnh segments.
in the meantime - if you only use the default segment sizes set in application preferences, you will get correct results. if you need to filter the package with non-default segment sizes you should turn multi-threading off when using such a filter in a compound filter.