-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boomer selects suboptimal solution in simple 3-node problem #158
Comments
I can confirm it's not avoiding any collapses, as if I reduce the ptable to omit 1 ie
then it correctly finds
|
I think the issue here is the high number of "windows" requested (100). Input rows are sorted according to their best probability, then the list of rows is chunked into the given number of windows. Across each independent run, shuffling occurs within each window, but the windows stay in the same total order. So it will always first add |
See the logging at the beginning of a run (with 100 windows requested):
The axioms in the first bin will always be added before proceeding to the next bin. Different runs will just shuffle the order of the two items in the second bin. |
my ticket is in error... more later |
I think we cleared this up. "windows" may not be as obvious as they ought to be but I think the UI will continue to evolve. |
still an issue
running yields
and an incoherent |
for text files see #157.
Given:
(in each case, the only other possibility is siblingOf)
note each class is in a separate prefix space, so there is no penalty for equivalence between any
Solutions:
boomer generally selects {1} depending on params, but never the optimal
I am pretty sure I have not made a typo - I put each class in its own ID space, so it is not avoiding 2 or 3 (which would happen if A/B/C were in the same ID space)
The text was updated successfully, but these errors were encountered: