JVET-M0001 JVET AHG report: Project management (AHG1) [J.-R. Ohm, G. J. Sullivan]

This document reported on the work of the JVET ad hoc group on Project Management, including an overall status report on the VVC standardization project and the progress made during the interim period since the preceding meeting.

At the 12th meeting of the ITU-T/ISO/IEC Joint Video Experts Team (JVET), an ad hoc group on Project Management was established with the following mandates:

• Coordinate overall JVET interim efforts.
• Supervise CE and AHG studies.
• Report on project status to JVET reflector.
• Provide a report to next meeting on project coordination status.

The reflector used for discussions by the JVET and all of its AHGs is the JVET reflector:
jvet@lists.rwth-aachen.de. For subscription to this list, see
http://mailman.rwth-aachen.de/mailman/listinfo/jvet.

In the interim period since the 12th JVET meeting, work towards finalizing the following (21) documents had been performed:

• JVET-L1001 Versatile Video Coding specification text (Draft 3)
• JVET-L1002 Algorithm description for Versatile Video Coding and Test Model 3 (VTM 3)
• JVET-L1004 Algorithm descriptions of projection format conversion and video quality metrics in 360Lib (Version 8)
• JVET-L1005 and JVET-L1006 Methodology and reporting template for coding tool testing and for neural network tool testing
• JVET-L1010, JVET-L1011, and JVET-L1012 JVET common test conditions and software reference configurations for SDR, HDR/WCG, and 360° video
• JVET-L1021 through JVET-L1033, descriptions of Core Experiments 1 through 13

The work of the JVET overall had proceeded well in the interim period, and many input documents had been submitted for consideration at the current meeting. Intense discussion had been carried out on the group email reflector, and all output documents from the preceding meeting had been produced.

As noted below, all output documents from the preceding meeting had been made available at the "Phenix" site (http://phenix.it-sudparis.eu/jvet/) or the ITU-based JCT-VC site (http://wftp3.itu.int/av-arch/jvet-site/2018_10_M_Macao/), although some of these documents were noted to potentially need further refinement:

• The meeting report (JVET-L1000) [Posted 2019-01-08]
• Versatile Video Coding (Draft 3) (JVET-L1001) [Posted 2018-10-31, last update 2019-01-08]
• Algorithm description for Versatile Video Coding and Test Model 3 (VTM 3) (JVET-L1002) [Posted 2018-12-03, last update 2018-12-24]
• Algorithm descriptions of projection format conversion and video quality metrics in 360Lib Version 8 (JVET-L1004) [Posted 2018-11-10]
• Methodology and reporting template for coding tool testing (JVET-L1005) [Posted 2018-10-27]
• Methodology and reporting template for neural network coding tool testing (JVET-L1006) [Posted 2018-10-25]
• JVET common test conditions and software reference configurations (JVET-L1010) [Posted 2018-11-16]
• JVET common test conditions and evaluation procedures for HDR/WCG video (JVET-L1011) [Posted 2018-11-20]
• JVET common test conditions and evaluation procedures for 360° video (JVET-L1012) [Posted 2018-11-19]

Description of CE 1..13 (JVET-L1021..35) [all first posted 2018-10-11 or 2018-10-12, further updated during the CE definition period of 3 weeks after the meeting, i.e., until 2018-11-02]. The following CE description documents had substantially later updates (more than 4 weeks after the meeting):

• JVET-L1022 [last updated 2019-01-08] (for which some experiment plans had changed and the change had been announced on the JVET reflector)
• JVET-L1023 [last updated 2018-12-27]
• JVET-L1024 [last updated 2019-01-08] (for which some experiment plans had changed but the change had not been announced on the JVET reflector)
• JVET-L1025 [last updated 2019-01-04]
• JVET-L1026 [last updated 2019-01-04]
• JVET-L1027 [last updated 2018-11-13]
• JVET-L1033 [last updated 2018-11-27]

The seventeen ad hoc groups had made progress, and reports from those activities had been submitted.

Software integration of the VTM was finalized approximately according to the plan.

Various problem reports relating to asserted bugs in the software, draft specification text, and reference encoder description had been submitted to an informal "bug tracking" system. That system is not intended as a replacement of our ordinary contribution submission process. However, the bug tracking system was considered to have been helpful to the software coordinators and text editors. The bug tracker reports had been automatically forwarded to the group email reflector, where the issues were discussed – and this is reported to have been helpful.

The software distribution had been migrated to GitLab before the previous meeting, and the method for obtaining access to the software had been changed after the last meeting – using shared accounts for read access by members (with one account for MPEG members using its usual credentials and another for VCEG members with access managed through the TIES system at the location https://www.itu.int/ifa/t/2017/sg16/exchange/wp3/q06/vceg_account.txt). The bug tracking system for software aspects was not integrated yet with GitLab for the time being.

At the time the meeting began, roughly 700 input contributions to the current meeting (not counting the AHG reports) had been registered for consideration at the meeting. Though the topics of Core Experiments and related documents for the development of low-level coding tools reflected the bulk of these documents, around 50 documents were submitted on aspects of high-level syntax, including tile partitioning.

A preliminary basis for the document subject allocation and meeting notes for the 13th meeting had been made publicly available on the ITU-hosted site.