Plastering Tool for PyRevit Elements

Tools Showcase
1

I’m Ammed Riveros Yupanqui, architect and BIM developer from Peru (AM3D.BIM.STUDIO). I built a Python tool for Revit that automates the modeling of tarrajeos (wall plaster/render finishes) — not just quantities. It generates the finish solids directly from the wall faces, resolves intersections and cuts between adjacent finishes, and handles complex geometry; quantities come out as a byproduct.

What motivates me is pyRevit’s spirit: free, open tools that support the whole community. I’d love to be part of that by donating this code so it becomes one of pyRevit’s built-in tools. I hand over the full code and documentation, and the dev team is completely free to improve, scale and stabilize it. I’ll keep supporting and answering questions along the way.

My only hope is that it stays free and open for the community — which is exactly why I’m bringing it to pyRevit and why I’m glad to release it under your GPL3 license.

Is there interest, and what’s the best way to submit it for review? Thanks for everything you do for the AEC world.

I’ve included a video demonstrating the development of this tool.

I look forward to your comments
— Ammed R.Y (AM3D.BIM.STUDIO)
—am3d.bim.studio@gmail.com

2

I’d set up a github location for your project, if you want feedback.

3

I had hoped the Pyrevit development team might integrate this code into their tools, but I see there is no interest, or perhaps this isn’t the right channel… at least I tried to contribute…

I appreciate your time…

4

Not that there isn’t interest. But there isn’t enough information to evaluate. One can’t review just a video. From the little that is posted, this seems a very specific tool and workflow. Most of the base pyRevit is general tools. Specific workflows and tools are picked up by extensions and grouped with other similar and related tools. This looks like a prime candidate for that.

The base tools of pyRevit are also primarily C# and python. Dynamo is more suited to extensions, as dyn version management is outside of what pyRevit can easily manage and see. That would need to be done in an extension.

1 Like
5

Not that we are not interested, on the contrary. The pyrevit team as you call it is neither fulltime on this or an entity in itself. Such a tool should be a separate extension of pyrevit IMHO. As Aaron said, this is a very specific tool.