addressed issue #1870
addressed issue #1870

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