-
Notifications
You must be signed in to change notification settings - Fork 74
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
Passing a reset signal to TMRegion from a Python region triggers an assert #1033
Comments
Oh, be careful here... However for the reset operation, we are only looking to see if it is 0 or something else. So if it is not 0 then it does the reset. I think, in most cases, the value will be either a 1 or a 0 and casting might accidentally get the correct answer just because a 0 is all bits off and a 1 value has some bits on in the lower part of the variable's field width. A better solution would be to do the following:
|
@dkeeney except for |
@fcr Sorry about the typo. |
Linking the reset signal from a Python region to a TMRegion in a HTMNetwork triggers the assert:
NTA_ASSERT(reset.getType() == NTA_BasicType_Real32)
in line 193 ofTMRegion.cpp
.The reset field in the output of the Python region is correctly of the type float32.
I am guessing that this may be a Numpy2 issue since this was not a problem with Numpy1.
I have temporarily removed this line from
TMRegion.cpp
and my project works correctly. Allhtm.core
unit tests still pass as well so this suggests that a test for this use case could be added.The text was updated successfully, but these errors were encountered: