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
..ok, probably not worth it, as scalar is more an example encoder. For real problems, one should use RDSE (which can encode categories the same way), and there this should not be applicable.
this is a good point. And with above "solved by RDSE", probably not worth hacking.
and I think that the spatial pool might have trouble recognizing "F"
this is a good point, an old issue. I think SP should be able to recognize and act on "no input" as some input. I'll make a separate issue for this. A solution on my mind, have a const random SDR that is encoded each time {} is on SP.compute()
In DateTime encoder #462 I noticed a field weekend is encoded as a Category (with scalar encoder).
Weekend is a binary field : T/F.
We use scalar encoder for categories, with radius=1(no overlap).
Say w=5.
T = [1111100000]
F = [0000011111]
This encoding makes sense for number of categories >2, but for binary cats, I'd prefer
T = [11111]
F = [00000]
Do we want to add such hack to Scalar?
The text was updated successfully, but these errors were encountered: