2016–17 Vijay Hazare Trophy Group D
2016–17 Vijay Hazare Trophy is the 15th season of the Vijay Hazare Trophy, a List A cricket tournament in India. It will be contested by 28 domestic cricket teams of India.[1][2]
| ||
|
| Dates | 25 February 2017 – 6 March 2017 |
|---|---|
| Administrator(s) | BCCI |
| Cricket format | List A cricket |
| Tournament format(s) | Round-robin and Playoff format |
| Host(s) | Kolkata |
| Participants | 7 |
| Matches played | 21 |
| Official website | Official website |
Points table
| Team | Pld | W | L | Tie | A | Pts | NRR |
|---|---|---|---|---|---|---|---|
| Chhattisgarh | 4 | 0 | 4 | 0 | 0 | 0 | 0 |
| Hyderabad | 4 | 0 | 4 | 0 | 0 | 0 | 0 |
| Jammu & Kashmir | 4 | 0 | 4 | 0 | 0 | 0 | 0 |
| Jharkhand | 4 | 3 | 1 | 0 | 0 | 6 | 2.65 |
| Karnataka | 3 | 3 | 0 | 0 | 0 | 0 | 0 |
| Saurashtra | 4 | 1 | 3 | 0 | 0 | 0 | 0.25 |
| Services | 4 | 0 | 4 | 0 | 0 | 0 | 0 |
Fixtures
Round 1
v |
||
- Pavan Deshpande, Krishnappa Gowtham, T Pradeep and Prasidh Krishna (Karnataka) all made their List A debuts.
v |
||
- Prerak Mankad, Kushang Patel, Abrar Shaikh (Saurashtra); Shakti Malviya, Poonam Poonia, Abhijit Salvi and Vipin Singh (Services) all made their List A debuts.
Round 2
26 February 2017 Scorecard |
v |
||
- Shubham Agarwal, Ashutosh Singh, Sahil Gupta, Kant Singh, Amandeep Khare, Shourabh Kharwar and Manoj Singh (Chhattisgarh) all made their List A debuts.
Round 3
28 February 2017 Scorecard |
v |
||
- Gaurav Kochar and Sachin Shinde (Services) both made their List A debuts.
Round 5
Round 6
4 March 2017 Scorecard |
v |
||
- Avnish Dhaliwal (Chhattisgarh), Sachidanand Pandey and Hitesh Solanki (Services) all made their List A debuts.
Round 7
6 March 2017 Scorecard |
v |
Jammu & Kashmir | |
- Anshuman Singh (Jammu & Kashmir) and Shasheem Rathour (Jharkhand) both made their List A debuts.
gollark: Try NodeOS!
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.
References
- "Tournament home". Archived from the original on 2017-02-23. Retrieved 2017-01-18.
- Fixtures @ Espncricinfo
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.