-
Notifications
You must be signed in to change notification settings - Fork 14
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
problems running local search algorithms #13
Comments
To clarify: The problems appear when usin aleph.pl. The problems do not show up (as far as I can see) when using aleph_orig.pl. This solves the concrete problem for me. |
Yes, it's a problem with porting, can you send me your input file? |
As I said, I'm happy now that it runs nicely with aleph.pl. However, since you might like to fix this in your port, here are the details: I use the attached file: Since i could not upload a *.pl file, i renamed the file extension to *.txt. You have to rename it back to cocktail2.pl I run it like this:
|
Should be fixed in the latest commit, 208adfa |
Hi, Thanks a lot for fixing this so quickly, yes, I checked, now it works nicely. Regards. Christian. |
Hello,
I was using your aleph port to get used to Aleph and its different search strategies. So thanks first of all, for providing the SWI-prolog version! This already helped a lot. However, when trying to run induce with local search settings, like this one, I get a warning and no results.
:- aleph_set(search, rls).
:- aleph_set(rls_type, gsat).
:- aleph_set(tries, 100).
:- aleph_set(moves, 10).
The warning is related to the call of
estimate_numbers(_)
It seems that the method which expectes two parameters exists, and that this can be easily fixed by changing to
estimate_numbers(_,M)
However, then another similar warning pops up related to another method call.
Maybe you forget to rewrite some methods calls when porting the code?
Sorry for maybe explaing this issue in a uncommon way. I'm not at all familar with prolog, so I refer to methods instead of goals.
Best regards,
Christian.
The text was updated successfully, but these errors were encountered: