search shadow

Add Element Properties to Clash Report / Clash Automation

Comments

4 comments

  • Avatar
    Laura Sharpe

    Thank you for sharing your example. I'll include it with the request.

    While I appreciate the extra steps you had to take to access the data you needed, including element data may significantly increase the time it takes to run a clash test, and might not make this type of improvement feasible. 

    0
    Comment actions Permalink
  • Avatar
    Jackson Murphy

    I have established a practice for these exact penetration type clash tests where we add the element properties into the group naming for the clash (i.e. name/rating of element a, and then the size, material, system, source file, etc. for element b). We can then export the clash list itself to excel and separate the clash names into columns by delimiter in excel. May be just a slightly less intensive workflow than the one you described John Jacob Paul.

    0
    Comment actions Permalink
  • Avatar
    John Jacob Paul

    Good one there, Jackson! I didn't realize we had the option to include property condition into clash group name. I am assuming you will also set grouping proximity very close (let's say 100mm) to ensure there is only one clash within a group?

    1
    Comment actions Permalink
  • Avatar
    Jackson Murphy

    We mostly use it for takeoff so I'm not too concerned with how many clashes get grouped together. However, that definitely seems like the best bet!

    0
    Comment actions Permalink

Please sign in to leave a comment.