addressed issue #1417
addressed issue #1417

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