Clash Batches

Clash Batches

The Batch tab of the Clash Detective control bar is used to manage your clash tests and results. You can set up as many tests as you like in a batch and save them into the JetStream .nwf file so that on opening it up again the tests can be re-run with the new model revision.

To run a clash test, either:

• Click on Update to run all of the tests in the batch.

or

• Select an existing test to run on its own, switch to the Select tab and click Start

Managing batches of clash tests

1. Click Add to append a new test to the current batch.

2. Click Delete to delete the currently selected test from the batch.

3. Click Compact to delete all clash results with a

   status
   of resolved from the test in order to create a smaller file.

4. Click Clean to reset all tests so that they are as if you had not yet run them. In other words, this will make their test status new.

5. Click Clear All to remove all tests from the batch in order to start from scratch.

Merging clash tests from multiple files

1. Merge the files using File, Merge . See the File Management, Merging Files section of the JetStream Roamer user guide for more information.

   All of the clash test data will be combined, whilst any duplicate geometry from the files will not be loaded.

Importing clash tests

Clash tests can be imported into JetStream Clash Detective to set up pre-defined, generic clash tests. (see >Exporting clash tests for information on exporting clash tests).

Note

If the clash test to be imported contains a search set as one of the clash selections, then the search set will also be imported along with all other test rules, options and selection information.

To import a clash test:

1. From the File menu, choose Import, Clash Test XML...

   The Import dialog is displayed:

   

2. Locate and Open the .xml file to import the clash test information, or click Cancel to return to JetStream.

Exporting clash tests

Tests can be set up to clash items based on generic properties, including direct property selection in the left and right clash selection trees, or using pre-defined search sets.

For example, you may have saved a search set that finds all pipes of a specific size, named "100mm Pipes". Your test then clashes all 100mm Pipes against the entire model (see ). Exporting this clash test will enable you to import it into another model, which will automatically set up a clash test between 100mm Pipes and the entire model.

Note

Any clash tests that are based on explicit selections will not be exported. For example, clashing one layer against another is not a valid test for exporting. To achieve this you will need to use the Find Items dialog to search for each layer based on a specific property (e.g. Item, Name). These searches can then be saved as Search Sets and finally selected in the Left and Right selection trees in Clash Detective.

You may also select all loaded files in the Left or Right selection tree and Clash Detective will treat this as selecting the entire model.

Multiple gereric tests can be set up as a batch and exported for use by other Clash Detective users or by yourself on other projects.

To export a clash test:

1. Having set up your implicit clash tests, from the File menu, choose Export, Clash Test XML...

   The Export dialog is displayed:

   

2. Enter a new file name and location, if you wish to change from those suggested.

3. Click Save to export the .xml file, or click Cancel to return to JetStream.

Creating custom clash tests

Exported clash tests can be used as a basis to define custom clash tests. If you have a common set of clash tests that you reuse on multiple projects, you can turn them into a custom clash test. Once installed as a custom clash test, the entire batch of tests can be selected and run directly from the Select tab. The results from all tests in the batch are combined and presented as the results of the custom clash test. The name of each test in the batch is displayed in the Description field of the results.

Custom clash tests are an excellent way to roll out a standardized set of tests across an organization. They allow the expertise of "power" users to be reused by everyone. Finally, they can be seen as a way of implementing object intelligence. For example, a custom clash test could be written that checked for compliance with a local building code based on object information and properties defined in a particular CAD system.

To define a custom clash test:

1. >Export your clash tests to an XML file. The name of the file is used as the default name of the custom test.

2. If desired, change the name of the custom test by editing the XML file directly. The top level element in the XML file is called "batchtest". The name of the custom test as displayed to the user is defined by the "name" attribute. The name of the custom test as saved in a file is defined by the "internal name" attribute.

3. To install the custom test, copy the exported XML file to the custom_clash_tests subdirectory of one of the JetStream search directories. Clash Detective searches these directories on startup looking for custom tests. See the section called "Search Directories" in the chapter called "Interface" in the Roamer book for more information.

4. To use the custom test select it from the Test Type drop down on the Select tab. And press Start . All other options and rules are specified by the custom test.