AI + GDL

[Patrick M]

I spent way too much time trying to teach chatbots, like chatgpt and gemini, the gdl help manuals/cookbook/etc... every script they threw at me was total garbage.
It turns out the 'full version' of claude is actually really useful for generating scripts, and even includes help guides for setting up parameter lists and trouble shooting bad script!

I threw a complex light fixutre together with a cut sheet, manuf. image, and a basic parameter:
"I need a light fixture from the attached cut sheet and image. It needs hotspots for each arm's angle and length. It needs a parameter for pendant length from the ceiling and a hotspot at the mounting point. max polygon count should be 15,000"

I didn't even need to request a 2d symbol, but I have no doubt it would edit the symbol to be whatever I need it to be given a few revised prompts.

I definitely recommend claude for GDL assistance!

object attached, for anyone curious.

Operating system used: Mac Apple Silicon

[Ahmed_K]

The perfect workflow for me so far is giving github the access to the libpacks, 

And it does the extraction process into xmls, and then with claude ai, you can apply any mass editing on the graphisoft library objects, and.it compiles back the edited objects to test thrm, 

This scope should be covered by archicad soo , this isa game changer, especially for doors and wi.dows

[Jeff Griffin]

I've also been experimenting with editing GDL using a paid Claude account.  In my work, I coordinate with structural engineers on custom home designs (log, timber and conventional framing) and using their structural markups, I'm responsible for developing both the architectural and structural drawing packages. I recently used Claude to modify my favorite GDL object of all time (Framing EMK 12, by Erich Karp). I've used this object for many years to model wooden rafters, joists and beams of several types. I asked Claude to take this already terrific framing object and add a few parameters that would help me in my daily work. Many hours later, and after lots of experimenting, the object is now has a GUI and is capable of showing more beam types, including steel shapes and round log members. It can also show members oriented vertically as columns. At a few points in this process, I asked Claude if it had any suggestions for improving the object and it usually had a few that I let it incorporate. At no point did Claude tell me that something couldn't be done. 

Objects oriented as columns can be shown as either solid material, or as built-up made from multi-ply 2x, LVL or LSL material.  The top and bottom of each individual ply can be adjusted by using grips in 3d, allowing me to easily show certain plies as trimmers and other plies as king studs. Previously, I used custom profile columns to show a multi-ply 2x, LVL or LSL column, but the individual plies couldn't be adjusted.  The top of the column (object) can be linked (with an offset) to the Home Story +1, Home Story +2 or Home Story +3. 

Previously, I needed to use the beam tool if I wanted to model a log beam or rafter. Tapering a log previously was done using the beam tool and setting the diameter at each end. Adding flats to a log typically required using a complex profile beam. There was no way that I am aware of to both taper a log, and add flats, aside from using SEOs to add the flats. I also wasn't able to schedule the length of sloped log beams. With this object, there is a parameter that allows me to set a taper (in inches) per 10 feet. There is also a toggle to orient the log so that the butt end of the log is at the low end. This object can incorporate flats on the top, bottom and each side of a log, without requiring any SEOs.

It has parameters to show the member type, size, quantity, on center spacing, length, pitch, etc. right on the plan.  The text can either be aligned with the object, or if multiple elements are shown, such as a repeating I-joist floor system as shown below, the text can run perpendicular to the framing, with an arrow. This arrow, framing type, quantity, on center spacing, length, slope can be individually turned on or off. This will make it easy for me to toggle this information on/off when reviewing layouts from lumber suppliers.  See below, showing a single placed object showing multiple framing elements and the optional (automatically generated) data describing the framing.

Taking it a step further, an optional built-in span checker was also incorporated. Since a majority of my work is in Michigan, I had Claude add a dropdown that allows me to choose which county the building site is located in so that it's able to use the exact snow load design values for that region, without requiring me to look at a snow load map. The interface also highlights the selected county on the map of my state. 

If I model a beam, rafter or joist system longer than what the span charts allow based upon the span, tributary width, dead load, live load & engineering properties of the member, the object displays a warning in red text indicating this. I'm able to have the object show the weight at each end, measured in kips.  Below, I've shown two beams (objects), one with centerline only and the other showing the entire beam, both with the weight at each end (total reaction, dead load and live load). Both beams were longer than the engineering properties allowed, so they show the warning in red text. 

I'm not a structural engineer and can't explain how the built-in span checker works, so I'll let Claude explain it.  See attached PDF if you are curious. 

I hope that this will be a good way for me to more accurately anticipate how deep a floor system should be modeled and/or how large a beam will need to be shown, prior to the structural engineer getting involved.

Sorry for the long read. I find this stuff to be  fascinating and I'm interested in reading how others are using this seemingly limitless technology.  I should also add that I don't know the first thing about GDL programming.