addressed issue #1797
addressed issue #1797

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