How do I remove one branch from JoinCrv result before feeding into Boundary Surfaces?

Grasshopper
,
#1

Hi, so I’m pretty new to Grasshopper, I was making a curved stairwell so I first made outlines for every step. I merged the four edges together (left edge, right edge, connecting widths) using JoinCrv but I’m left with a single line at the end because it doesn’t have any other geometry to connect to.

This is the far end of my Grasshopper set-up, and one branch says Line-like curve at the end of the panel connected to the Join component.

image
image1270×769 115 KB

For reference, here’s the result. It’s actually fine, but the extra invisible line at the end will cause problems if I try to use the BoundarySrf result for other components.

image
image460×770 12.5 KB

How do I remove the last line/branch from the JoinCrv panel that says “Line-like Curve”?

Also if anyone’s kind enough how do I move them sequentially upwards for stair riser height? Thank you!

Here’s my GH file:
stairs.gh (16.9 KB)

#2

You didn’t internalize your curves.

By the way, renaming standard components is counter-productive in my experience. Better to rename outputs instead of the components.

1 Like
#3

Oh. I still wasn’t familiar with internalization. How does it work?

And noted on the renaming. Thank you!

#4

Or post the related Rhino .3dm file, preferably saved as R6 format.

#5

stairs R6.3dm (172.8 KB)

Here, sir! Thank you!

#6

One curve is still missing:

missing
missing1060×521 58.3 KB

#7

Oh, the curve attributed there is the one horizontal line there at the base of the main curve. My bad.
stairsupdated.gh (14.1 KB)

#8

Here’s another way…

Canvas at 21;36;46
Canvas at 21;36;461434×659 163 KB

stairs_re.gh (9.4 KB)

1 Like
#9

I figured that out. It’s easy to see why this happens. I used an expedient shortcut to get around it.

stairs_2021_Jul2a
stairs_2021_Jul2a.gh (10.4 KB)

P.S. This version has the curves internalized.

stairs_2021_Jul2a2.gh (10.9 KB)

1 Like
#10

Thank you! Will use this as another iteration.

#11

Thank you sir! Was just studying the first one you sent me. Thank you! I’ll marked this solved.

#12

Unfortunately, there is a problem. The steps are out of sequence after SrfSplit so I had to sort them (white group).

stairs_2021_Jul2b
stairs_2021_Jul2b1196×558 160 KB

stairs_2021_Jul2b.gh (17.3 KB)

1 Like
#13

Yet another method, closer to your original approach and question. This doesn’t use SrfSplit so doesn’t require Sort Along Curve, though it looks more complex, eh? One simplification is to use Divide Curve instead of DivLength.

stairs_2021_Jul2c
stairs_2021_Jul2c1563×722 201 KB

stairs_2021_Jul2c.gh (29.6 KB)

1 Like
#14

Thank you for all your replies, master! I’ll study the latest one too.

#15

Foolish of me not to add Prune Tree to your original code! (yellow group)

stairs_2021_Jul2d
stairs_2021_Jul2d689×719 71.8 KB

stairs_2021_Jul2d.gh (18.3 KB)

1 Like
#16

Whoah. Info overload :laughing: ! Thank you! Will study these as well.

#17

Version ‘d’ is the simplest answer to your question in the thread title:

How do I remove one branch from JoinCrv result before feeding into Boundary Surfaces?

:man_facepalming: Prune to keep only the branches with four curves and ignore the branch with only one curve.

1 Like
#18

Yeah I figured when I opened it. Nonetheless, the additional workarounds taught me a lot too!

#19

This was a classic example of jumping to a conclusion (“a shortcut”) that painted myself into a corner, requiring “extraordinary measures” (sorting) to get out of it. Software is like that, hence the many revisions. Sorry about the info overload.

This is my final offer, I promise! :wink: Shortest List instead of Prune Tree.

stairs_2021_Jul2e
stairs_2021_Jul2e1424×556 108 KB

stairs_2021_Jul2e.gh (22.9 KB)

Simpler? Curves are internalized.

1 Like