fixed issue #858
fixed issue #858

USGSDenverPychron/pychron,NMGRL/pychron,UManPychron/pychron,UManPychron/pychron,NMGRL/pychron,NMGRL/pychron,UManPychron/pychron,USGSDenverPychron/pychron,NMGRL/pychron,UManPychron/pychron,USGSDenverPychron/pychron,USGSDenverPychron/pychron