addressed issue #964
addressed issue #964

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