powered by CADENAS



3.3.6.  Test project / Test directory

Before projects are transferred to the directory tree of PARTdataManager or get Status 5 under SVN Administration (see Section, “Level 4”), new entries or changes have to be checked for any errors via Test project. You can choose from a large number of test criteria.

The results of this check are logged in a log. This information allows you to make the required corrections in targeted manner.

Via the context menu, open Test projects in directory . Der The command refers to the respective location of the Test project or Test directory .

Test projects in directory

Test projects in directory

The option buttons in detail

  • Find unused files : ...finds all files which are not assigned to a project. You can either allocate such files to a project or delete them.

[Note] Note

Please note that supposedly unused files may possibly be used in other directories. You should thus delete only files which you are quite certain are no longer required!

  • Calculate geometry : this function builds up the attributes (table rows) of all geometries (*.3db drawing files) on a trial basis. Attributes which lead to an “impossible” structure, such as a negative value for width across flats, are logged as an error. As the title already says, the associated calculation process may take a very long time.

  • Test geometry on CAD compatibility : this checks the component geometry for geometrical integrity.

  • Test value ranges

  • Test standard part identifier : The standard part identifier, e.g. ’Hexagon nut DIN 1587 $ NENN.’ (in the title bar of PARTdataManager) which you have entered in PARTeditor (identification data) may, under certain circumstances, be incomplete or incorrect. For example, if column values (representing an element of the standard part identifier) prompted for in certain rows are not present.

  • Test standard part identifier for uniqueness : ...compares all standard part identifiers which may occur as the result of the various attributes (rows). If a standard part identifier occurs more than once, it is not unique. --> You must adapt the standard part identifier so that it is always unique!

  • Test short name : During the export of parts from PARTsolutions to different CAD systems, it is normal for the Standard Name to be adopted as part name. As certain CAD systems have a string limit, alternatively the Brief Description is applied.

    The short name is a "reduced" (preferably as short as possible) version of the Standard Name, limited to the maximum length (16 characters according to CAD).

    If the string of a short name is larger than this limit, an entry is created in the log file.

  • Test short name based on uniqueness : the short name must also be unique, as must the standard part identifier.

  • Test name of project files for uniqueness : the name of every *.prj file must also be unique since, otherwise, an assembly may use “the wrong one” if there are two identically named *.prj files (with different content).

  • Test standard numbers for uniqueness: this excludes standard numbers occurring more than once.

  • Find unused variables in 3db files : ...checks all *.3db files belonging to the selected directory in order to establish whether they contain variables which are not used. The variables found may be identified in the log and then deleted if applicable.

  • Delete unused variables in 3db files : if this option is checked, the variables found with Find unused variables in 3db filesare deleted directly.

[Important] Important

What counts for files, also counts for variables. Please remember that possibly unused variables may be linked to assemblies. Therefore only delete variables where you are absolutely sure that they are no longer needed.

  • Test bitmaps : PARTproject sets a limit for the bitmaps used as a preview. This limit is 100 x 100 pixels and 256 colors. Images which exceed this limit are recorded in the log. The file size (and, thus, the loading time) of the bitmap can be reduced accordingly using conventional image editing programs.

  • Create protocol : the test run log may record either all project rows checked (Log file) or only the wrong project rows (Error file). Check the Create protocol option button. --> Enter the required log file location, including the extension (e.g. *.txt) in the Log file or Error filefield.

  • Create metafiles : ...creates a file in PARTsolutions export format *.ps3. This file can be imported in the relevant CAD system using the corresponding menu command of the PARTsolutions interface. The Destination directory field (file location of the ps3 file) can be activated by checking the Create metafiles option.

  • Maximum time for one row : ..., that should be permitted for the buildup of a single *.3db part geometry (per model). A limit of 5 minutes is recommended. If the limit is exceeded an entry in the log file follows. Check the relevant geometries and if so, make the necessary corrections in their creation.

By clicking OK the selected test criteria will be used and the test run will be started.

[Note] Note

The test run for extensive directories may take several hours under certain circumstances. It is advisable to run the test either overnight or on a separate computer.