# "Constrained" swarming

**URL:** <https://discourse.numenta.org/t/constrained-swarming/972>\
**Category:** NuPIC\
**Tags:** swarming\
**Created:** [July 10, 2016, 11:30pm UTC](https://discourse.numenta.org/t/constrained-swarming/972 "2016-07-10T23:30:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![scott](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/scott/32/170_2.png) [@scott](https://discourse.numenta.org/u/scott)\
**Post date:** [July 13, 2016, 12:22am UTC](https://discourse.numenta.org/t/constrained-swarming/972/4 "2016-07-13T00:22:49Z")

</div>

While Matt prefers the simplified JSON interface to swarming, the [description.py/permutations.py](http://description.py/permutations.py) interface is the primary way to do swarming currently and gives much more control over the model parameters and what is swarmed over. The [permutations.py](http://permutations.py) variables specify a range to try for each parameter and the values that it tries override values in the base [description.py](http://description.py) so simply leaving things out of the permutations file should achieve your goal of a more constrained swarm.

It’s true that documentation is limited though. You can start with Ron’s video and then modify an existing example that has [description.py](http://description.py) and [permutations.py](http://permutations.py) files.

---

_[View the full topic](https://discourse.numenta.org/t/constrained-swarming/972)._