2017 Tour de Corse
Thierry Neuville and Nicolas Gilsoul were the rally winners. Their team, Hyundai Shell Mobis WRT, were the manufacturers' winners.[1]
2017 Tour de Corse 60. Che Guevara Energy Drink Tour de Corse 2017 | |||
---|---|---|---|
Round 4 of the 2017 World Rally Championship
| |||
Host country | |||
Rally base | |||
Dates run | 6 – 9 April 2017 | ||
Stages | 10 (316.80 km; 196.85 miles) | ||
Stage surface | Tarmac | ||
Results | |||
Overall winner | |||
Crews | 78 at start, 58 at finish |
Entry list
Classification
Event standings
Pos. | No. | Driver | Co-driver | Team | Car | Class | Time | Difference | Points |
---|---|---|---|---|---|---|---|---|---|
1 | 5 | Hyundai i20 Coupe WRC | WRC | 3:22:53.4 | 0.0 | 26 | |||
2 | 1 | Ford Fiesta WRC | WRC | 3:23:48.1 | +54.7 | 22 | |||
3 | 6 | Hyundai i20 Coupe WRC | WRC | 3:23:49.4 | +56.0 | 17 | |||
4 | 10 | Toyota Yaris WRC | WRC | 3:24:03.0 | +1:09.6 | 17 | |||
5 | 8 | Citroën C3 WRC | WRC | 3:24:03.1 | +1:09.7 | 13 | |||
6 | 4 | Hyundai i20 Coupe WRC | WRC | 3:25:09.7 | +2:16.3 | 8 | |||
7 | 32 | Škoda Fabia R5 | WRC-2 | 3:31:04.1 | +8:10.7 | 6 | |||
8 | 34 | Ford Fiesta R5 | WRC-2 | 3:32:10.4 | +9:17.0 | 4 | |||
9 | 84 | Škoda Fabia R5 | 3:32:17.0 | +9:23.6 | 2 | ||||
10 | 44 | Citroën DS3 R5 | WRC-2 | 3:35:50.5 | +12:57.1 | 1 |
Special stages
Day | Stage | Name | Length | Winner | Car | Time | Rally Leader |
---|---|---|---|---|---|---|---|
Leg 1 (7 Apr) | SS1 | Pietrosella – Albitreccia 1 | 31.20 km | Citroën C3 WRC | 19:56.5 | ||
SS2 | Plage du Liamone – Sarrola Carcopino 1 | 29.12 km | Citroën C3 WRC | 18:22.3 | |||
SS3 | Pietrosella – Albitreccia 2 | 31.20 km | Ford Fiesta WRC | 19:52.1 | |||
SS4 | Plage du Liamone – Sarrola Carcopino 2 | 29.12 km | Citroën C3 WRC | 18:20.4 | |||
Leg 2 (8 Apr) | SS5 | La Porta – Valle di Rostino 1 | 48.71 km | Hyundai i20 Coupe WRC | 32:19.6 | ||
SS6 | Novella 1 | 17.27 km | Hyundai i20 Coupe WRC | 11:13.1 | |||
SS7 | La Porta – Valle di Rostino 2 | 48.71 km | Ford Fiesta WRC | 32:15.9 | |||
SS8 | Novella 2 | 17.27 km | Hyundai i20 Coupe WRC | 11:17.7 | |||
Leg 3 (9 Apr) | SS9 | Antisanti – Poggio di Nazza | 53.78 km | Hyundai i20 Coupe WRC | 32:34.6 | ||
SS10 | Porto Vecchio – Palombaggia [Power Stage] | 10.42 km | Toyota Yaris WRC | 6:02.2 | |||
Power Stage
The Power Stage was a 10.42 km (6.5 mi) stage at the end of the rally.
Pos. | Driver | Co-driver | Car | Time | Diff. | Pts. |
---|---|---|---|---|---|---|
1 | Toyota Yaris WRC | 6:02.2 | 5 | |||
2 | Ford Fiesta WRC | 6:03.0 | +0.8 | 4 | ||
3 | Citroën C3 WRC | 6:04.3 | +2.1 | 3 | ||
4 | Hyundai i20 Coupe WRC | 6:06.8 | +4.6 | 2 | ||
5 | Hyundai i20 Coupe WRC | 6:08.6 | +6.4 | 1 | ||
Championship standings after the rally
|
|
gollark: Or Great Information Transfer.
gollark: Git stands for GIT Is Tremendous.
gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.
gollark: UPDATE: this is wrong.
gollark: > Git uses delta encoding to store some of the objects in packfiles. However, you don't want to have to play back every single change ever on a given file in order to get the current version, so Git also has occasional snapshots of the file contents stored as well. "Resolving deltas" is the step that deals with making sure all of that stays consistent.
References
- "Sunday In Corsica: Neuville Breaks Victory Jinx". wrc.com. WRC Promoter GmbH. Retrieved 16 March 2018.
- "2017 Entry List". ewrc-results.com. ewrc-results.com. Retrieved 8 April 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.