Conference P1450.3 Working Group
Friday, August 30, 1:15 to
1. TRC errors
2. 1450.4 and channel mapping
3. Change Signals to SignalCharacteristics
Detailed error descriptions of potential TRC errors are currently defined
in each section and Annex G summarizes. It was decided that error numbering
should *not* be in the standard. It was then further decided that exact
wording of error messages should *not* be in the document. A section should
be included on expectation of tools that perform TRC checks and how they
are expected to report errors. Errors should be identified by the hierarchical
block/statement name. e.g., TRC.PatternCharacteristics.MaxVectors.
P1450.4 is looking into some aspects that may overlap with P1450.3. In
particular tester channel mapping using NameMaps, and MultiplePort/MultipleSite
definitions. More discussion with other team is required.
Decided to change Signals to SignalCharacteristics to be consistent with
other block names of this standard.
A brief discussion (again) on Dan's tutorial. Group thought that it was
of appropriate size and detail, although a full review has not been done.
Group agreed to include it in the standard and continue the review process.
Topics for next meeting (Friday 9/13/2002)
Topics for discussion at next meeting:
FM-1 - tutorial review
JT-5 - LoopCharacteristics - review changes and approve
Remainder of resolution issues
1. Tony - Include Dan's tutorial (dated May 24, 2002) into the doc
2. Tony - Remove TRC error messages and add section on TRC error reporting
3. Tony - Close out draft-04 and start draft-05
4. Tony - Review Dan's examples of resource-id labels and include in