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
{{ message }}
This repository has been archived by the owner on Dec 31, 2020. It is now read-only.
River View rivers come in two varieties - scalar and geospatial. It is unclear (to me) what extra work is needed to support geospatial rivers - maybe nothing. Please test the RiverSource against one (here's a possible list).
The text was updated successfully, but these errors were encountered:
There is one big problem with geospatial rivers that is not current solved by the current geospatial encoding mechanism in NuPIC and HTM.Java: Encoding events occurring in space time is different than encoding an object moving over time. The current encoding mechanism was designed for the 2nd case. All of the geospatial rivers in River View are of the 1st type.
So you are not going to get much out of solving this issue until NuPIC or HTM.Java have an enhanced geospatial encoder for events, not objects.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
River View rivers come in two varieties - scalar and geospatial. It is unclear (to me) what extra work is needed to support geospatial rivers - maybe nothing. Please test the RiverSource against one (here's a possible list).
The text was updated successfully, but these errors were encountered: