2016 Internationaux de Tennis de Vendée – Singles
Benoît Paire was the defending champion but lost in the semifinals to Andrey Rublev.
Singles | |
---|---|
2016 Internationaux de Tennis de Vendée | |
2015 Champion | ![]() |
Champion | ![]() |
Final score | 7–5, 2–6, 6–3 |
Julien Benneteau won the title after defeating Rublev 7–5, 2–6, 6–3 in the final.
Seeds
Benoît Paire (Semifinals) Mikhail Youzhny (First round) Paul-Henri Mathieu (First round) Konstantin Kravchuk (Second round) Radu Albot (Second round) Nikoloz Basilashvili (First round) Marco Chiudinelli (Second round) Tobias Kamke (First round)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
Finals
Semifinals | Final | ||||||||||||
1/WC | ![]() | 3 | 613 | ||||||||||
![]() | 6 | 715 | |||||||||||
![]() | 5 | 6 | 3 | ||||||||||
![]() | 7 | 2 | 6 | ||||||||||
![]() | 65 | 66 | |||||||||||
![]() | 77 | 78 | |||||||||||
Top half
First Round | Second Round | Quarterfinals | Semifinals | ||||||||||||||||||||||||
1/WC | ![]() | 6 | 6 | ||||||||||||||||||||||||
![]() | 4 | 3 | 1/WC | ![]() | 78 | 61 | 6 | ||||||||||||||||||||
![]() | 3 | 6 | 6 | ![]() | 66 | 77 | 1 | ||||||||||||||||||||
![]() | 6 | 4 | 3 | 1/WC | ![]() | 4 | 6 | 6 | |||||||||||||||||||
![]() | 6 | 66 | 6 | ![]() | 6 | 3 | 2 | ||||||||||||||||||||
![]() | 4 | 78 | 1 | ![]() | 77 | 6 | |||||||||||||||||||||
![]() | 77 | 6 | ![]() | 64 | 3 | ||||||||||||||||||||||
8 | ![]() | 65 | 3 | 1/WC | ![]() | 3 | 613 | ||||||||||||||||||||
3 | ![]() | 4 | 6 | 66 | ![]() | 6 | 715 | ||||||||||||||||||||
![]() | 6 | 1 | 78 | ![]() | 6 | 6 | |||||||||||||||||||||
![]() | 2 | 6 | 715 | ![]() | 4 | 4 | |||||||||||||||||||||
![]() | 6 | 4 | 613 | ![]() | 4 | 4 | |||||||||||||||||||||
![]() | 6 | 4 | 7 | ![]() | 6 | 6 | |||||||||||||||||||||
Q | ![]() | 4 | 6 | 5 | ![]() | 7 | 6 | ||||||||||||||||||||
Q | ![]() | 6 | 6 | Q | ![]() | 5 | 4 | ||||||||||||||||||||
6 | ![]() | 2 | 4 |
Bottom half
First Round | Second Round | Quarterfinals | Semifinals | ||||||||||||||||||||||||
5 | ![]() | 6 | 6 | ||||||||||||||||||||||||
Q | ![]() | 3 | 3 | 5 | ![]() | 3 | 712 | 4 | |||||||||||||||||||
SE | ![]() | 6 | 6 | SE | ![]() | 6 | 610 | 6 | |||||||||||||||||||
WC | ![]() | 1 | 3 | SE | ![]() | 1 | 3 | ||||||||||||||||||||
![]() | 6 | 7 | ![]() | 6 | 6 | ||||||||||||||||||||||
![]() | 4 | 5 | ![]() | 6 | 6 | ||||||||||||||||||||||
![]() | 4 | 5 | 4 | ![]() | 4 | 3 | |||||||||||||||||||||
4 | ![]() | 6 | 7 | ![]() | 65 | 66 | |||||||||||||||||||||
7 | ![]() | 3 | 6 | 6 | ![]() | 77 | 78 | ||||||||||||||||||||
WC | ![]() | 6 | 1 | 4 | 7 | ![]() | 4 | 3 | |||||||||||||||||||
![]() | 77 | 6 | ![]() | 6 | 6 | ||||||||||||||||||||||
![]() | 63 | 3 | ![]() | 2 | 4 | ||||||||||||||||||||||
![]() | 6 | 6 | ![]() | 6 | 6 | ||||||||||||||||||||||
Q | ![]() | 4 | 4 | ![]() | 6 | 3 | 5 | ||||||||||||||||||||
![]() | 6 | 64 | 77 | ![]() | 4 | 6 | 7 | ||||||||||||||||||||
2/WC | ![]() | 4 | 77 | 64 |
gollark: ... no.
gollark: Thus bad.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.