| Plan for Test Model development
Our plan is to establish a "Test Model 1.0" in October.
The "Test Model" will contain only the minimum set of well-tested tools that together form a coherent design that is confirmed to show good capability. The "minimum set" may include such variations as would be appropriate for forming multiple profiles of the design.
What we have now is a "TMuC". The concept of the TMuC may still exist after October.
The TMuC is a "rough best guess" of a set of tools that has appeared to show promise.
The TMuC may contain some duplications/overlaps/variations of functionality that we would not accept in the confirmed Test Model.
Our current TEs are planned to be performed relative to "reference configurations" of the TMuC selected for the set of sequences in the CfP test set with the planned QP set (see JCTVC-B120 and this report).
In regard to the evaluation of tools that are already in the TMuC, the inclusion of something in the "reference configuration" setting should not be construed as a selection of technology that needs less analysis and justification than any other feature.
In principle, it is agreed that it should be possible to switch off any coding "tool" that is in the TMuC, either in the config file or in TypeDef.h.
Dostları ilə paylaş: | 
