addressed issue #1475
addressed issue #1475

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