So I now have the full detail on how the batch assembly zones work.
In short, it's primary value is for situations when the assembly is too large to load into session in one go. If you can load the assembly completely then the batch zones add no real value here.
Anyway to describe how they work...
There's no real performance benefit when using zones as the loading and unloading of parts into session negates any benefit. During any clearance analysis (if zones are used or not) components are checked by their bounding boxes and ignored if they clearly do not intersect.
A good method for performance and general efficiency would be to run in Lightweight mode first with a larger clearance zone than required (to account for the faceting tolerance). Then re-run in exact mode on interfering components (MB3-->Do Solid Check).
Another minor thing is to keep the top assembly up-to-date (save it after the analysis). So when you open it up again, the clearance set knows which bodies have actually changed/moved since last time, and it can avoid reanalyzing stuff that didn’t change.
(credit to Mike Nelson for helping with the detailed response)
I want to run several sets in batch.
what is the way to do it?
I try this:
"v:\aeapps\ug\NX12\nxbin\ug_clearance" -n="SET1" -r="report-set1.log" "C:\DATA\OF01-WTB2\OF01-WTB2.prt"
"v:\aeapps\ug\NX12\nxbin\ug_clearance" -n="SET2" -r="report-set2.log" "C:\DATA\OF01-WTB2\OF01-WTB2.prt"
You are right @1u7obd Tomas.
And not forgetting the other exclusion options like 'Exclude Pairs within Same Subassembliy' should give you the same result in your engine room / generator example.
With some thought, a number of clearance sets can be saved for an assembly and reusued throughout the design interations.