addressed issue #1852
addressed issue #1852

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