Page 1 of 1
How to make HoneySearch work with OCA?
Posted: June 1st, 2019, 5:09 am
by testitemqlstudop
Replacing the rule in the last lines (the line initiating the HoneySearch object) didn't work:
gol.hatsya.co.uk/census/b2i34cj6a7c8s2-i3-a4ceit6in/SS
Re: How to make HoneySearch work with OCA?
Posted: June 3rd, 2019, 8:17 am
by testitemqlstudop
Okay, if there is no way, can I be informed of that?
Re: How to make HoneySearch work with OCA?
Posted: June 3rd, 2019, 10:02 am
by apg
testitemqlstudop wrote:Okay, if there is no way, can I be informed of that?
There's certainly no trivial way at the moment.
I can't remember enough of the internal implementation of HoneySearch to be able to answer that question fully. It's definitely the case that only p1/p2 intermediates are supported as target objects, and only
Glider 115 is supported as the glider. As far as I know, those are the only 'deep' assumptions; any other rule-based assumptions are 'shallow' ones such as hardcoded rulestrings. But HoneySearch was written 2.5 years ago, so I have only a murky memory of the details.
In any case, you'll need to build lifelib for the target rule. Whereas apgsearch does this automatically with recompile.sh, you'll need to find the line from recompile.sh which calls python, and run that in the slmake base directory to switch the local lifelib rule. Indeed, you probably want to update the lifelib in the repository -- it's currently version 2.0.22, which is far behind 2.2.20 (the latest lifelib).