zlacker

[parent] [thread] 3 comments
1. amorzo+(OP)[view] [source] 2025-12-05 20:16:33
Can you give an example of the sort of harness you used for that? Would love to play around with it
replies(1): >>knolli+wd
2. knolli+wd[view] [source] 2025-12-05 21:25:03
>>amorzo+(OP)
I've been using pyrevit inside revit so I just threw a basic loop in there. There's already a building model and the coworkers are just placing and wiring outlets, switches, etc. The harness wasn't impressive enough to share (alos contains vibe coded UI since I didn't want to learn XAML stuff on a friday night). Nothing fancy; I'm not very skilled (I work in construction)

I gave it some custom methods it could call, including "get_available_families", "place family instance", "scan_geometry" (reads model walls into LLM by wall endpoint), and "get_view_scale".

The task is basically copy the building engineer's layout onto the architect model by placing my families. It requires reading the symbol list, and you give it a pdf that contains the room.

Notably, it even used a GFCI family when it noticed it was a bathroom (I had told it to check NEC code, implying outlet spacing).

replies(1): >>ftcHn+BF
◧◩
3. ftcHn+BF[view] [source] [discussion] 2025-12-06 00:30:21
>>knolli+wd
I'm going to try to get it to generate extrusions in Revit based on images of floor plans. I've tried doing this in bunch of models without success so far.
replies(1): >>knolli+GS
◧◩◪
4. knolli+GS[view] [source] [discussion] 2025-12-06 02:41:13
>>ftcHn+BF
You might want to give it some guidance based on edge centers? It'll have a hard time thinking of wall thickness and have it draw points if you're trying to copy floor plans.

for clarity now that I'm rereading: it understands vectors a lot better than areas. Encoding it like that seems to work better for me.

[go to top]