{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/8f972cf4f9504d0f97dc83909a99086d\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/8f972cf4f9504d0f97dc83909a99086d-c03a4e6481025add.gif","duration":788.875,"title":"Day 16 - Crash-n-Clash - 03 - Code","description":"In this video, I walk you through the process of creating a proof of concept for the Crash and Clash tool, focusing on detecting intersections between pipes and walls. We start with a simple project setup, using a filtered element collector to get our pipes and then applying an intersection filter to identify any clashes. I also demonstrate how to adapt the tool for different categories, like floors, to ensure versatility. I encourage you to test this with various elements and scenarios to see how it performs. Please make sure to follow along and implement the changes as we go!"}