2015–16 Tahiti Ligue 1
The 2015–16 Tahiti Ligue 1 is the 69th season of top-flight football in Tahiti.[1] Tefana are the defending champions having won their fourth title last season.
| Season | 2015–16 |
|---|---|
← 2014–15 2016–17 → | |
Teams
A total of eight sides will compete in the 2015–16 campaign. The top side will qualify for a place in the 2017 OFC Champions League, while the bottom two will be relegated to Tahiti Ligue 2.
| Team | Stadium | Location | Capacity | Manager |
|---|---|---|---|---|
| Aorai | Stade De Taunoa | Papeete | 1,000 | |
| Central Sport | Stade Pater Te Hono Nui | Pirae | 15,000 | |
| Dragon | Stade Vélodrome Dr. Pierre Cassiau | Papeete | 5,000 | Ludovic Graugnard |
| Manu-Ura | Stade Paea | Paea | 10,000 | Pita Teivitau |
| Pirae | Stade Vélodrome Dr. Pierre Cassiau | Papeete | 5,000 | Samuel Garcia |
| Taiarapu | Stade Teahupo'o | Teahupo'o | 1,200 | |
| Tefana | Stade Louis Ganivet | Faaa | 5,000 | Sébastien Labayen |
| Vénus | Stade Pater Te Hono Nui | Pirae | 15,000 |
League table
| Pos | Team | Pld | W | D | L | GF | GA | GD | BP | Pts | Qualification or relegation |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Tefana (C) | 21 | 19 | 2 | 0 | 103 | 20 | +83 | 4 | 84 | Qualified to the 2017 OFC Champions League |
| 2 | Central Sport | 21 | 11 | 1 | 9 | 48 | 51 | −3 | 10 | 65 | |
| 3 | Vénus | 21 | 9 | 6 | 6 | 45 | 42 | +3 | 8 | 62 | Qualified to the Championship Playoff |
| 4 | Pirae | 21 | 10 | 1 | 10 | 58 | 62 | −4 | 10 | 62 | |
| 5 | Manu-Ura | 21 | 11 | 3 | 7 | 48 | 48 | 0 | 2 | 59 | |
| 6 | Dragon | 21 | 4 | 7 | 10 | 41 | 53 | −12 | 6 | 46 | |
| 7 | Taiarapu (R) | 21 | 3 | 4 | 14 | 39 | 68 | −29 | 10 | 44 | Relegation to Tahiti Ligue 2 |
| 8 | Aorai (R) | 21 | 3 | 4 | 14 | 23 | 61 | −38 | 2 | 36 |
Updated to match(es) played on 21 March 2016. Source: RSSSF
Rules for classification: 1) points; 2) goal difference; 3) number of goals scored. 4 points for a win, 2 points for a draw, 1 point for a defeat.
(C) Champion; (R) Relegated.
Rules for classification: 1) points; 2) goal difference; 3) number of goals scored. 4 points for a win, 2 points for a draw, 1 point for a defeat.
(C) Champion; (R) Relegated.
Championship playoff
Bracket
| Semi-finals | Final | |||||
| 28 March | ||||||
| Tefana | 6 | |||||
| 23 April | ||||||
| Pirae | 1 | |||||
| Tefana (p) | 1 (6) | |||||
| 28 March | ||||||
| Central Sport | 1 (5) | |||||
| Central Sport | 4 | |||||
| Vénus | 0 | |||||
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.
gollark: A lot?
gollark: probably.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.