addressed issue #1908
addressed issue #1908

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