Closed linas closed 9 years ago
Humm.. I didn't get the blow up, instead I get segmentation fault on calling Instantiator. Must be related to https://github.com/opencog/atomspace/commit/f287fd78a1484b6aac22cc4a1795e3b508e1b2a6
Happens when trying to Instantiate
(InheritanceLink (stv 1.000000 0.000000)
(VariableNode "$Z") ; [128]
(ConceptNode "green") ; [130]
) ; [131]
with mapping
(VariableNode "$Z") ; [128]
----->
(QuoteLink (stv 1.000000 0.000000)
(VariableNode "$Z") ; [128]
) ; [190]
I need to understand what the change to the Instantiator is doing first.
The URECommons has nothing to do with it, since BackwardChainer doesn't use URECommons at all (I guess it is not really "common".)
Oh, that's interesting. I'm guessing that the instantiator did not notice that there is a QuoteLink there, and went into infinite regress, substituting for Z. Right? Is that what you are implying? QuoteLinks are suppose to be a "don't go past this spot" marker, but the instantiator code is old, pre-dating the quotelinks, and probably was never modified to track them.
I can fix that quick, if that is what you think is happening, just not tonight.
The Instantiator is not suppose to care about QuoteLink right?
I am using it to quickly recreate an atom and replace some sub-atoms using my own mapping (in this case want to wrap a QuoteLink around the VariableNode). It could have easily been something other than QuoteLink (like (ListLink (Var $Z))).
I guess if the Instantiator is to become more and more specialized for PM's purpose, I should recreate a simplified version for my use...?
URECommons compiles and passes for me, has anything been fixed? Can that issue be closed?
William, Instantiator should care about QuoteLink. It should not instantiate anytyhing under quote link
Nil, I commented out a bunch of URECommmons code to get it to compile. Any, none of teh URE-related unit tests pass.
On Mon, May 18, 2015 at 4:05 AM, ngeiswei notifications@github.com wrote:
URECommons compiles and passes for me, has anything been fixed? Can that issue be closed?
— Reply to this email directly or view it on GitHub https://github.com/opencog/atomspace/issues/41#issuecomment-102982189.
They used to pass last Friday, we've got to identify what commit makes them fail.
I've just tried f287fd7 but at some point (I don't know which test) myRAM got overloaded and I had to restart my system.
I am pretty sure URECommons test is failed by https://github.com/opencog/atomspace/commit/72cad99be855561cc9538ce6f0fc05e8c33a97ff which I believe @misgeatgit is already fixing (by looking at his branch).
and BackwardChainer test is by f287fd7 as mentioned above.
OK. And on my side I could observe that at 9737528 nothing (except RuleUTest) breaks.
I have a fix for that but am trying to figure out why ForwardChainerUTest is failing on my machine. The previous failed due to some methods I removed in a commit I removed a bunch of obsolute ones from the URECommons. On May 18, 2015 5:42 PM, "ngeiswei" notifications@github.com wrote:
OK. And on my side I could observe that at 9737528 https://github.com/opencog/atomspace/commit/9737528afea7674aa05f72930a12aefc3cb8d021 nothing (except RuleUTest) breaks.
— Reply to this email directly or view it on GitHub https://github.com/opencog/atomspace/issues/41#issuecomment-102997321.
yes 72cad99 is the one that broke the build
I think I understand why f287fd7 is triggering the break, but it will take me another 6-8 hours for a proper fix. This change exposes multiple issues.
Closing. Between pull req #45 and #44 I think this is resolved. I get this:
Start 60: RuleUTest
60/75 Test #60: RuleUTest .............................***Failed 1.34 sec
Start 61: ForwardChainerUTest
61/75 Test #61: ForwardChainerUTest ................... Passed 0.45 sec
Start 62: BackwardChainerUTest
62/75 Test #62: BackwardChainerUTest .................. Passed 0.69 sec
Start 63: URECommonsUTest
63/75 Test #63: URECommonsUTest ....................... Passed 0.44 sec
Start 64: JsonicControlPolicyParamLoaderUTest
64/75 Test #64: JsonicControlPolicyParamLoaderUTest ... Passed 0.35 sec
Start 65: DefaultForwardChainerCBUTest
65/75 Test #65: DefaultForwardChainerCBUTest .......... Passed 0.34 sec
Start 66: FCMemoryUTest
66/75 Test #66: FCMemoryUTest ......................... Passed 0.24 sec
I also get
36 - ExecutionOutputUTest (Failed)
48 - EvaluationUTest (Failed)
but that is my fault. will try too fix soon.
Thanks, Linas!
I think I'm done messing with atomspace internals for a while. I hope. I had to fix-up, add, tweak things to get them to work right, but that seems to be done now.
The URECommons unit tests do not compile. After some minimal hacs to stub out the parts that don't compile, the BackwardChainerUTest blows up: it uses up all available RAM in about 60 seconds, and then grinds the swap disk. Am disabling these for now.