addressed issue #1682
addressed issue #1682

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