2018 KPIT MSLTA Challenger

2018 KPIT MSLTA Challenger
Date	19 – 24 November
Edition	5th
Draw	32S / 16D
Surface	Hard
Location	Shree Shiv Chhatrapati Sports Complex, Pune, India
Champions
Singles
	Elias Ymer
Doubles
	Vijay Sundar Prashanth / Ramkumar Ramanathan

The 2018 KPIT MSLTA Challenger was a professional tennis tournament played on hard courts. It was the fifth edition of the tournament which was part of the 2018 ATP Challenger Tour. It took place in Pune, India from 19 to 24 November 2018.

Singles main draw entrants

Seeds

Country	Player	Rank¹	Seed
MDA	Radu Albot	101	1
IND	Ramkumar Ramanathan	124	2
SWE	Elias Ymer	132	3
IND	Prajnesh Gunneswaran	144	4
AUS	Marc Polmans	145	5
GBR	Jay Clarke	174	6
SVK	Andrej Martin	189	7
GBR	James Ward	199	8

¹ Rankings are as of 12 November 2018.

Other Entrants

The following players received wildcards into the singles main draw:

Aryan Goveas
Arjun Kadhe
Sasikumar Mukund
Manish Sureshkumar

The following player received entry into the singles main draw as a special exempt:

Saketh Myneni

The following player received entry into the singles main draw as an alternate:

Nicola Kuhn

The following players received entry from the qualifying draw:

Sebastian Fanselow
Lucas Gerch
Ben Patael
Francesco Vilardo

The following player received entry as a lucky loser:

Benjamin Hassan

Champions

Singles

Elias Ymer def. Prajnesh Gunneswaran 6–2, 7–5.

Doubles

Vijay Sundar Prashanth / Ramkumar Ramanathan def. Hsieh Cheng-peng / Yang Tsung-hua 7–6^(7–3), 6–7^(5–7), [10–7].

gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.

gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.

gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.

gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.

gollark: But I suppose I could drop the text bit, that can be reconstructed later™ and search doesn't really need it.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.