You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding a call to self.ConfigPats() in the ra25.py demo project (from .../leabra/examples/ra25/) entering into the function call patgen.PermutedBinaryRows(dt.Cols[1], 6, 1, 0) (~line 766) ends up in etable.py where env is a missing variable. When I add the from' line locally and then did .../leabra/python/make install' (Important: do not do a make since that appears to restore the env-less version) it appears to fix the problem, only to seg fault further downstream (see .../emer/leabra/ Issue #1).
The text was updated successfully, but these errors were encountered:
this is a bug in gopy, which I'll have to fix at some point soon. I was able to fix this specific issue by moving the order of etable in front of emergent in the gopy command in leabra/python/Makefile, but then another one cropped up involving agg. it just needs smarter logic on these imports.
This was fixed in pr198 of gopy which has yet to be applied. In case anyone else is looking at this, you need to do this in gopy to get the update:
$ cd~/go/src/github.com/go-python/gopy # use $GOPATH instead of ~/go if somewhere else
$ git fetch origin pull/198/head:pr198 # this gets the pull-request #198, into branch pr198
$ git checkout pr198 # switch to that branch
$ go install # do go get -u ./... if this fails and try again -- installs gopy exe in ~go/bin
After adding a call to self.ConfigPats() in the ra25.py demo project (from
.../leabra/examples/ra25/
) entering into the function callpatgen.PermutedBinaryRows(dt.Cols[1], 6, 1, 0)
(~line 766) ends up inetable.py
where env is a missing variable. When I add thefrom' line locally and then did
.../leabra/python/make install' (Important: do not do amake
since that appears to restore the env-less version) it appears to fix the problem, only to seg fault further downstream (see.../emer/leabra/
Issue #1).The text was updated successfully, but these errors were encountered: