Dimensional Measuring Interface
Standard
Standard Improvement Request
|
SIR No. 97-29 DMIS Release 3.0 SIR Type Other Severity Documentation Deficiency Status Resolved Date Submitted March 6 1997 Date Validated March 6 1997 Date In Process Date Referred June 28 1998 Date Vote Pending Date Closed August 20 1998 Action Clarifications Submitted By Dietmar May Object Workshops, Inc. PO Box 597 Whytheville VA 24382 USA Phone: (540)223-1145 Fax: (540)223-1241 dcmay@object-workshops.com |
Problem Topic
SNSET: Trailing specification?
Problem Description
SNSET/ ~var4~, defined as ~,var1~ would allow a single one of the first
five ~var1~ parameters to be specified in a trailing context, but only one
(eg, SNSET/FOCUSY, SCALEX, 0.75, APPRCH, 1.0). The first five ~var1~
parameters appear to be intended for stand-alone use. Is this trailing
specification intended and legal?
References
None
Related SIRs
None
Suggested Resolution
[This SIR has been referred to the Sensor SME Working Group for further research.]
Support Documentation
None
Resolution
Warning!!
The following statement is only a resolution to a Standard Improvement Request (SIR) and is NOT part of the current DMIS standard, nor is it guaranteed to become part of the next revision of the DMIS standard even if voted and accepted by the DMIS National Standards Committee. This resolution is tentative because it may not be incorporated into the next version of the standard, it could be changed prior to the next release, or it could be changed as the result of the "public review and comment" period required for the next version of the standard. If you choose to use this tentative resolution, you do so at your own risk since at this time it is not part of the DMIS standard.
Added note to SNSET and modified SNSET input format.
The trailing specification is intended and legal.
Change to the standard:
Add Note (page 152) at the end:"APPRCH, RETRCT, SEARCH, CLRSRF, DEPTH,SCALEX, and SCALEY may only appear once within a single SNSET statement. FOCUSY and FOCUSN can only appear once within a single SNSET statement and are mutually exclusive."
Additionally, input format will be changed to :
SNSET/var_1 var_4
and all references to var_4 in var_1 description will be removed.
Attachments
None
Notes
Added by Mike Holloway, hkm@ornl.gov on 7/30/1998
No reference was found in meeting minutes that this SIR was referred.
It looks like SNSET needs some rework. It seems to me that most of the var_1 arguments can be used at most once in a SNSET statement. The exceptions are VL() and FOCUSY/FOCUSN. Multiple lighting definitions could possibly be used for a given sensor (this is contrary to what I said when commenting on a previous SIR). To prevent ambiguity, multiple lights would need to be specified in a single SNSET statement. A new SNSET statement that defined new lighting conditions (for a given carriage) would replace previous light(s).
The other case, FOCUSY/FOCUSN, would need to be binary in a SNSET statement. Only one of the two should be allowed.
For the first 5 possible arguments, I don't see why they could not all be specified in a single SNSET statement. The standard as it now reads does not allow this.
To correct these problems, we may need to have a var_x for each of the individual arguments and define them appropriately.
Added by Interpretation Sub-Committee, gph5@chrysler.com on 8/5/1998
The trailing specification is intended and legal.
Change to the standard: Add Note (page 152) at the end: "APPRCH, RETRCT, SEARCH, CLRSRF, DEPTH, SCALEX, and SCALEY may only appear once within a single SNSET statement. FOCUSY and FOCUSN can only appear once within a single SNSET statement and are mutually exclusive."
Added by DNSC, rui@ornl.gov on 8/6/1998
The trailing specification is intended and legal. Change to the standard: Add Note (page 152) at the end:"APPRCH, RETRCT, SEARCH, CLRSRF, DEPTH,SCALEX, and SCALEY may only appear once within a single SNSET statement. FOCUSY and FOCUSN can only appear once within a single SNSET statement and are mutually exclusive."
Additionally, input format will be changed to :
SNSET/var_1 var_4
and all references to var_4 in var_1 description will be removed.