addressed issue #1661
addressed issue #1661

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