addressed issue #899
addressed issue #899

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