# Anomaly detection from multiple variable

**URL:** <https://discourse.numenta.org/t/anomaly-detection-from-multiple-variable/2670>\
**Category:** NuPIC\
**Tags:** question\
**Created:** [August 11, 2017, 2:15am UTC](https://discourse.numenta.org/t/anomaly-detection-from-multiple-variable/2670 "2017-08-11T02:15:26Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![rhyolight](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/rhyolight/32/3922_2.png) [@rhyolight](https://discourse.numenta.org/u/rhyolight)\
**Post date:** [August 11, 2017, 3:11pm UTC](https://discourse.numenta.org/t/anomaly-detection-from-multiple-variable/2670/6 "2017-08-11T15:11:16Z")

</div>

> [@z-wony](#):
>
> I will study and try it as your recommend.

Remember that there have been some breaking changes in NuPIC since then, so the code I wrote in that video will not work if you’re using recent versions of NuPIC. See:

> [@WARNING: 0.7.0 breaking changes](https://discourse.numenta.org/t/warning-0-7-0-breaking-changes/2200):
>
> We will be making a number of breaking changes with 0.7, because we are prepping for a 1.0 release this year, and we have code that needs major refactoring, which will affect serialization, API usage, and parameter names. This is a necessary growing pain NuPIC needs to move forward. How to upgrade: Find / replace in your codebase: tpParams ==\> tmParams tpEnable ==\> tmEnable How to upgrade: Find / replace in your codebase: CLAModel ==\> HTMPredictionModel clamodel ==\> htmpredi…

---

_[View the full topic](https://discourse.numenta.org/t/anomaly-detection-from-multiple-variable/2670)._