文件列表:

NISTI++DMEtestSuite3.0 (0, 2004-08-20)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents (0, 2004-08-18)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts (0, 2004-08-18)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\CATIA (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\CATIA\DaimlerChryslerTestPart.CATPart (3696359, 2003-12-09)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\DMIS (0, 2004-08-18)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\DMIS\IMTS_M_clean.dmi (5002, 2004-08-18)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\I++ (0, 2004-08-18)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\I++\DCXpart.prg (7157, 2004-08-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\I++\DCXpart.res (23215, 2004-08-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\I++\DCXpart.txt (2180, 2004-08-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\IGES (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\IGES\DaimlerChryslerTestPart.igs (599830, 2003-12-09)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\picture (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\picture\dc_test_part_solid.jpg (143286, 2004-03-30)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\picture\dc_test_part_wire.jpg (143056, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\STEP_AP203 (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\STEP_AP203\daimlerchryslertestpartap203.log (5090, 2003-12-09)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\STEP_AP203\DaimlerChryslerTestPartAP203.stp (288563, 2003-12-09)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\STEP_AP214 (0, 2004-08-16)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\DCXpart\STEP_AP214\DaimlerChryslerTestPartAP214.stp (294580, 2003-12-09)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\ACIS10.0 (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\ACIS10.0\ipp_simple11.sat (5771, 2003-12-04)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\DMIS (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\DMIS\output.dms (210, 2003-12-03)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\DMIS\simple_in.dms (1299, 2003-12-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\I++ (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\I++\simple.prg (1015, 2003-12-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\I++\simple.res (1086, 2003-12-17)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\IGES (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\IGES\ipp_simple.igs (40672, 2003-12-04)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\IGES\ipp_simple__out.log.1 (1912, 2003-12-04)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\Parasolid (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\Parasolid\ipp_simple.xmt_txt (3972, 2003-12-02)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\picture (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\picture\ipp_simple.ps (38173, 2003-12-02)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\ProEngineer (0, 2004-07-22)
NISTI++DMEtestSuite3.0\standAloneTestSuiteComponents\artifacts\IPlusSimplePart\ProEngineer\ipp_simple.drw.2 (26494, 2004-01-15)
... ...

The test_files directory contains files for testing implementations of the I++ DME Interface specficiation, version 1.4. Files with a .prg suffix are command files. Most of these are intended to be used to test command parsers (normally found inside servers). Some of them are intended to be executed by a server to test the entire server. The syntax of command strings and command files is described in documents named command_string_spec and prg_file_spec. There is a .prg test file for every command in the spec. If the command is named XXX, the .prg test file is named XXX.prg and focuses on testing the XXX command. Files with a .res suffix are response files. Most of these are intended to be used to test response parsers (normally found inside clients). The syntax of response strings and response files is described in documents named response_string_spec and res_file_spec. There is a .res test file for every type of response that can be made by a server. Files with a .txt suffix are text files that describe the corresponding .prg and/or .res files. In most cases there are three related files with the same base name but different suffixes (.prg, .res, and .txt). In these case the .res file is what might be returned by a server when the client runs the .prg file, and the .txt file gives a general description of the other two files. Some of the test programs are intended to trigger errors in a command parser or response parser. In these cases there may be only two related files. The following .prg files are intended to be completely executable. To use these files, it is necessary in most cases to have a specific physical artifact in place on the CMM being controlled. Read the .txt file to see what is needed. These files are written in part coordinates based on an assumed machine coordinate system. The files may be edited automatically (using the PCSmover utility) to use some other machine coordinate system. See the documentation for PCSmover. NO FILES YET.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：