addressed issue #1571
addressed issue #1571

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