addressed issue #1584
addressed issue #1584

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