Help optimizing components in a cluster component to run faster

Grasshopper
, , , ,
1

Hi All,

I have made this cluster component to create a parametric street canyon that has the following inputs :

image
image759×503 69.5 KB

and then outputs Shading surfaces, Sidewalks, Streets, Probing Point, Walls, custom Probing Plane, and context Surfaces.

Inside is pretty simple, but it is lengthy and I am wondering if someone can help me to optimize it. I am 99% sure that there is a lot in here that can be simplified, I am just a noob at this and do not know exactly how to go about it/what can be/what cannot be.

This part makes the shading on top

image
image1445×210 45.4 KB

This makes the sidewalks and Street, so that if you make the sidewalk wider, the street gets narrower

image
image1186×254 40.8 KB

Here I make the canyon surfaces themselves, a lot of copying tho:

image
image1330×276 47.8 KB

And then I find the center of the canyon to make a probing point, probing plane, and make everything rotateable (for street orientation)

image
image659×673 46.2 KB

Right now it takes about 196ms to run the component, which seems like a lot to me? Maybe it is not. Regardless, I would love to simplify the component anyway.

Any help would be much appreciated. Script attached.
ParametricStreetCanyon.gh (36.9 KB)

2

missing

I don’t see any reason for this to be a cluster?

3

I’m sorry, what do you mean by this? The component you reference is one singular component to find the center of something :

image
image1242×664 69 KB

4

What I mean is that the Heteroptera plugin is required so anyone who doesn’t want to install it won’t be able to help.

5

Oh I see. So sorry. Here is an updated version w/ a stock rhino center component
ParametricStreetCanyon.gh (41.2 KB)

6

This has fewer components, though is not fully optimized as it might be simplified further.

Fixed a problem with Offset Curve by providing a ‘P’ (Plane) input.

ParametricStreetCanyon_2021_Jun21a.gh (31.5 KB)