addressed issue #1859
addressed issue #1859

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