addressed issue #1083
addressed issue #1083

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