addressed issue #1566
addressed issue #1566

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