I'm doing clash testing on a machine. The machine is imported as one STEP file, which has about 50 subgroups making up the main parts. Every main part in turn has about 1-30 subparts making up that part in particular.
What I want to do is to test the first level of parts (the main ones) against each other.
Testing the entire STEP file against itself yields hundreds of clashes, where most of them are self intersecting within one main part. I've created selection sets for every main part, but testing all sets against all sets means that every set will test against itself and thus include internal clashes.
Testing one set against all others work, but that means 50 tests.
A rule similar to "ignore clashes in same selection set" would be great, but the only rule that comes close is "items which are both in selection set '<set>'", where <set> has to be specified to one particular set, meaning I would have to create one rule for each selection set, i.e. 50.
Is there any good solution to this problem?
It sounds like you are checking "Self Intersect" on the Select tab of the Clash Detective. Uncheck the box "Self-Intersect" and the selected SS will not clash itself.
Ok, good. Clears that question.
I suspect you will be having to do the 50 or so batches. Nice thing though, set the batch jobs up just one time, maintain the NWF, and you won't have to re-create with any changes and updates to the models. There are other tools too, like the Batch Utility that can help you to automate the process.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!