Skip to content

Instantly share code, notes, and snippets.

@marty1885
Last active August 5, 2019 16:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save marty1885/e7f5eacb17a1c328cf0f4ae2ed9ea648 to your computer and use it in GitHub Desktop.
Save marty1885/e7f5eacb17a1c328cf0f4ae2ed9ea648 to your computer and use it in GitHub Desktop.
Etaler_API_example.ipynb
Display the source blob
Display the rendered blob
Raw
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@marty1885
Copy link
Author

marty1885 commented Aug 5, 2019

your suggested command but got error:

ROOT is not installed by default on Ubuntu based systems. Nor is it is the official repository. I installed it via Arch Linux's repo (I run Arch)

sudo pamcan -S root

You'll have to build ROOT yourself if you are on Ubuntu/Debian. @alior101, have you got a minute? I'm not sure how to build ROOT on Ubuntu/Debian.

@marty1885
Copy link
Author

marty1885 commented Aug 5, 2019

Etaler has too many changes from nupic that it will be difficult for you to troubleshoot what caused the changes.

There are some changes I know is causing the differences.

First, Etaler implements the original TM algorithm back from 2011 and updating to the new connect-to-all method. While NuPIC uses the updated TM algorithm from 2016 (but still staying on the old connect-once method). Secondly, I didn't set the hyper parameters in Etaler to what NuPIC has. Third, NuPIC uses anomaly likelihood while Etaler uses the raw anomaly score (as I haven't implement that yet)

@alior101
Copy link

alior101 commented Aug 5, 2019 via email

@cyberslam
Copy link

cyberslam commented Aug 5, 2019 via email

@marty1885
Copy link
Author

marty1885 commented Aug 5, 2019

@cyberslam You might want to check your email settings and edit your post. The format os way off and other data is leaking trough.

@cyberslam
Copy link

cyberslam commented Aug 5, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment