# Debugging CoordinateEncoder issues in NuPIC 1.0

**URL:** <https://discourse.numenta.org/t/debugging-coordinateencoder-issues-in-nupic-1-0/2656>\
**Category:** NuPIC\
**Created:** [August 8, 2017, 4:16am UTC](https://discourse.numenta.org/t/debugging-coordinateencoder-issues-in-nupic-1-0/2656 "2017-08-08T04:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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 8, 2017, 5:01pm UTC](https://discourse.numenta.org/t/debugging-coordinateencoder-issues-in-nupic-1-0/2656/4 "2017-08-08T17:01:17Z")

</div>

Are you trying to resurrect an old model saved in an older version of NuPIC? Because that will not work because we broke backwards compatibility:

> [@Would breaking NuPIC serialization backwards compatibility affect you?](https://discourse.numenta.org/t/would-breaking-nupic-serialization-backwards-compatibility-affect-you/1452):
>
> NuPIC models can be serialized to disk. Many people do this to save their models in case of failure, to stop and restart them for performance reasons, or to save them for later times. Breaking backwards compatibility of this serialization technique means that any current models saved using the old method could not be resurrected in any version of NuPIC after the backwards compatible change was made. [1] The ability to break serialization backwards compatibility would untie our hands in many wa…

---

_[View the full topic](https://discourse.numenta.org/t/debugging-coordinateencoder-issues-in-nupic-1-0/2656)._