Closed marinier closed 11 years ago
Fixed in rete-srand-patch branch.
When the child nodes of a ReteNode are read in, they're head-inserted into the list of children, i.e., inserted in the reverse order than they appear in the (j)rete file.
CSoar seems to have the same issue and we'll probably need to back port our change.
Confirmed fixed.
FYI, I've posted the bug to csoar, along with the change you made so hopefully they will be able to duplicate your fix easily.
On Tue, Mar 19, 2013 at 6:02 PM, cnewton notifications@github.com wrote:
Fixed in rete-srand-patch branch.
When the child nodes of a ReteNode are read in, they're head-inserted into the list of children, i.e., inserted in the reverse order than they appear in the (j)rete file.
CSoar seems to have the same issue and we'll probably need to back port our change.
— Reply to this email directly or view it on GitHubhttps://github.com/soartech/jsoar/issues/94#issuecomment-15146260 .
I guess I shouldn't close this until the change has been pushed to the public repo.
To reproduce:
Expected: finishes in 27 dcs. Actual: runs much, much longer (I think it actually gets in an infinite loop, which is not necessarily related).
Somehow, loading rules with rete-net is changing the way the random seed affects operator selection? Huh?