International organisation for standardisation organisation internationale de normalisation

20Core Experiment planning and Common Conditions

20.1General issues for CEs

Because the first working draft and HEVC test model (referred to as the HM) have now been selected, group coordinated experiments are now referred to as "core experiments" rather than "tool experiments".

A preliminary CE description is to be approved at the meeting at which the CE plan is established.

It is possible to define sub-experiments within particular CEs, for example designated as CE X.a, CE X.b, etc., for a CE X, where X is the basic CE number.

As a general rule, it was agreed that each CE should be run under the same testing conditions using one software codebase, which should be based on the HM software codebase. The general agreed common conditions for experiments were described in the output document JCTVC-C500.

A deadline of twp weeks after the meeting was established for organizations to express their interest in participating in a CE to the CE coordinators and for finalization of the CE descriptions by the CE coordinator with the assistance and consensus of the CE participants.

Final CEs should clearly describe specific tests to be performed, not describe vague activities. Activities of a less specific nature are delegated to Ad Hoc Groups rather than designated as CEs.

Experiment descriptions should be written in a way such that it is understood as a JCT-VC output document (written "third party perspective", not a company proponent perspective). The experiment descriptions should generally not express opinions or suggest conclusions – rather, they should just describe what technology will be tested, how it will be tested, who will participate, etc.

CE descriptions should not contain verbose descriptions of a technology (at least not unless the technology is not adequately documented elsewhere). Instead, the CE descriptions should refer to the relevant proposal contributions for any necessary further detail. However, the complete detail of what technology will be tested must be available – either in the CE description itself or in referenced documents that are also available in the JCT-VC document archive.

Those who proposed technology in the respective context (by this or the previous meeting) can propose a CE or CE sub-experiment. Harmonizations of multiple such proposals and minor refinements of proposed technology may also be considered. Other subjects would not be designated as CEs.

Any technology must have at least one cross-check partner to establish a CE – a single proponent is not enough. It is highly desirable have more than just one proponent and one cross-checker.

It is strongly recommended to plan resources carefully and not waste time on technology that may have little benefit – it is also within the responsibility of the CE coordinator to take care of this.

CE participants are obligated to submit a report of the results of their experiment testing and any further analysis of the subject matter. Each participant is required to submit a report – measures will be taken if this principle is violated without good reason.

A summary report written by the coordinator (with the assistance of the participants) is also expected to be provided to the subsequent meeting.

Non-final CE plan documents were reviewed and given tentative approval during the meeting.

The particular CEs planned at this meeting were documented in the documents numbered JCTVC-C5xx, with xx = 01, 02, etc.

The CE description for each planned CE is described in an associated output document JCTVC-B3xx for CExx, where "xx" is the CE number.

It must be understood that the JCT-VC is not obliged to accept the test methodology or outcome of a CE as being adequate. Good results from a CE do not impose an obligation on the group to accept the result (e.g., if the expert judgment of the group is that further data is needed or that the test methodology was flawed).

20.2Common Conditions

Preferred Common Conditions for experiment testing that are intended to be appropriate for both CEs and other experiments were selected by the group and described in output document JCTVC-C500.

21Output documents

The following documents were agreed to be produced as outputs of the meeting. Names recorded below indicate those responsible for document production.

21.1.1.1.1.1.1.1.1JCTVC-C400 Meeting Report of 3^rd JCTVC Meeting [G. J. Sullivan, J.-R. Ohm]

21.1.1.1.1.1.1.1.2JCTVC-C401 The process of Test Model development for the HEVC initiative [G. J. Sullivan, J.-R. Ohm]

21.1.1.1.1.1.1.1.3JCTVC-C402 High Efficiency Video Coding (HEVC) Test Model 1 (HM 1) Encoder Description [K. McCann (primary), B. Bross, S. Sekiguchi]

21.1.1.1.1.1.1.1.4JCTVC-C403 High Efficiency Video Coding (HEVC) text specification Working Draft 1 [T. Wiegand (primary), W.-J. Han, G. J. Sullivan, J.-R. Ohm]

21.1.1.1.1.1.1.1.5JCTVC-C404 HEVC Software guidelines [D. Flynn, K. Sühring]

21.1.1.1.1.1.1.1.6JCTVC-C405 Summary of HEVC Model (HM) and Working Draft 1 [T.K. Tan, G. J. Sullivan , J.-R. Ohm]

21.1.1.1.1.1.1.1.7JCTVC-C500 Common HM test conditions and software reference configurations [F. Bossen]

21.1.1.1.1.1.1.1.8JCTVC-C501 Core Experiment 1: Decoder-side Motion Vector Derivation [Y.-J. Chiu (primary), H. Yu, Y.-W. Huang, S. Sekiguchi]

21.1.1.1.1.1.1.1.9JCTVC-C502 Core Experiment 2: Flexible Motion Partitioning [E. Francois (primary), X. Zheng, P. Chen]

21.1.1.1.1.1.1.1.10JCTVC-C503 Core Experiment 3: Interpolation for MC (Luma) [T. Chujoh]

21.1.1.1.1.1.1.1.11JCTVC-C504 Core Experiment 4: Interpolation for MC (Chroma) [E. Alshina (primary), Y.-L. Lee, P. Chen, H. Lakshman]

21.1.1.1.1.1.1.1.12JCTVC-C505 Core Experiment 5: Low Complexity Entropy Coding Improvement [X. Wang]

21.1.1.1.1.1.1.1.13JCTVC-C506 Core Experiment 6: Intra prediction improvements [A. Tabatabai (primary), A. Tanizawa, A. Segall, H. Yu, S. Lei, J. Xu, J. Chen, Y.-J. Jeon, G. Li, M. Mrak]

21.1.1.1.1.1.1.1.14JCTVC-C507 Core Experiment 7: Alternative transforms [R. Cohen (primary), C. Yeo, R. Joshi]

21.1.1.1.1.1.1.1.15JCTVC-C508 Core Experiment 8: In-Loop filtering [T. Yamakage (primary), T. Chujoh, Y. W. Huang, K. Chono, I. S. Chong, T. Yamamoto, J. Lim, B. Jeon, J. Xu, M. Narroschke]

21.1.1.1.1.1.1.1.16JCTVC-C509 Core Experiment 9: MV coding [J. Jung, B. Bross]

21.1.1.1.1.1.1.1.17JCTVC-C510 Core Experiment 10: Number of Intra Prediction Directions [K. Sugimoto]

21.1.1.1.1.1.1.1.18JCTVC-C511 Core Experiment 11: Coefficient Scanning and Coding [V. Sze (primary), K. Panusopone, J. Chen, T. Nguyen, M. Coban]

21.1.1.1.1.1.1.1.19JCTVC-C512 Core Experiment 12: Adaptive Motion Vector Resolution [W.-J. Chien]

21.1.1.1.1.1.1.1.20JCTVC-C513 Core Experiment 13: Intra Smoothing [M. Coban (primary), B. Bross, J. Chen]