The Joint Collaborative Team on Video Coding (jct-vc) of itu-t wp3/16 and iso/iec jtc 1/sc 29/wg 11 held its second meeting during 21-28 July, 2010 at the itu-t premises in Geneva, ch

8TE planning

8.1General issues for TEs

As a general rule, it was agreed that each TE should be run under the same testing conditions using one software codebase. The general agreed common conditions for experiments were described in the output document JCTVC-B300, as further detailed below.

It is possible to define sub-experiments within particular TEs, eg. TE.xa, TE.xb, etc.

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

A deadline of August 9 was established to express interest in participating in a TE, with finalization of the TE descriptions by August 13 (5 days after the planned availability of TMuC version 0.6).

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.

Those who proposed technology in the respective context (by this or the previous meeting) can propose a TE or TE sub-experiment. Other subjects would not be designated as TEs.

Any technology must have a cross-check partner to establish a TE – 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 TE coordinator to take care of this.

Each participant is required to submit a report – measures will be taken if this principle is violated without good reason.

A summary report by the coordinator is expected to be provided to the subsequent meeting.

Particular TEs planned at this meeting are summarized in the following subsections of this report.

A particularly important TE is TE12, for testing of the individual coding tools in the TMuC.

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

Good results from a TE 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).