# Parameter optimization with htm.core

**URL:** https://discourse.numenta.org/t/parameter-optimization-with-htm-core/6668
**Category:** NuPIC Community Fork
**Created:** [October 4, 2019, 10:42pm UTC](https://discourse.numenta.org/t/parameter-optimization-with-htm-core/6668 "2019-10-04T22:42:09Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![bmaneiki](https://avatars.discourse-cdn.com/v4/letter/b/a8b319/32.png) [@bmaneiki](https://discourse.numenta.org/u/bmaneiki)
#### Post date: [October 4, 2019, 10:42pm UTC](https://discourse.numenta.org/t/parameter-optimization-with-htm-core/6668/1 "2019-10-04T22:42:09Z")

</div>

I am new to HTM and I have a few newbie getting started questions. I am using python.

I am getting very different results with the hotgym example in python from htm.core and putting it in HTM Studio. HTM Studio detects a lot fewer anomolies and I am interested in how to optimize the parameters I am using for the encoder, SP and TM.

With htm.core, how should I do parameter optimization? Should I use swarming?

I am struggling with figuring out how to use Network API with htm.core? Specifically, I am not sure what regions are available or how to use them without reading the source. Is there documentation or an example for this?

I am having problems using the example hotgym example with other csv files using larger numbers. For example, I took the nyc\_taxi.csv file from HTM Studio and it starts to consume all my memory when it gets to large numbers around 30,000 or so and I have to kill the process.

Does anyone have any tips for me?

Thanks,  
Brian

---

<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: [October 7, 2019, 4:51pm UTC](https://discourse.numenta.org/t/parameter-optimization-with-htm-core/6668/2 "2019-10-07T16:51:22Z")

</div>

> [@bmaneiki](#):
>
> I am getting very different results with the hotgym example in python from htm.core and putting it in HTM Studio.

If I remember correctly, the algorithm behind HTM Studio’s anomaly detection is the `BacktrackingTM`, which is an older version of sequence memory that employs some non-biological methods. I do not think this logic was ported into htm.core (@dmac @David_Keeney correct me if I’m wrong). So I would not expect you would get the same results from these two systems.

---

<div class="post-metadata">

### Author: ![David\_Keeney](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/david_keeney/32/1616_2.png) [@David\_Keeney](https://discourse.numenta.org/u/David_Keeney)
#### Post date: [October 7, 2019, 8:16pm UTC](https://discourse.numenta.org/t/parameter-optimization-with-htm-core/6668/3 "2019-10-07T20:16:19Z")

</div>

BacktrackingTM was ported to htm.core but was later removed because it was not biological.

I am not sure which TM was used in the original hotgym example but the TM in htm.core my use parameters slightly differently so that could cause differences as well. @dmac or @breznak could give more insight on this.
