List replace/swap/weave/etc...???

Replies to This Discussion

Permalink Reply by Danny Boyes on April 22, 2014 at 10:35pm

I would just use the [replace text] component. Text to search for = true. Text to replace with = closed planar curve.

Permalink Reply by Seb on April 22, 2014 at 10:50pm

Hey Danny,

Thanks for the reply! This doesnt seem to work. I am trying to eliminate actual curves they are not texts. Sorry for the confusion. 

Permalink Reply by Danny Boyes on April 23, 2014 at 1:25am

Do you actually want a null in their place?

Permalink Reply by Seb on April 23, 2014 at 1:35am

Hi Danny,

I will use this list as an input.

Whenever it says closed planar curves (or true), I want the command to run.

Whenever it says planar curve or invalid curve (or false), I want the command to skip.

Permalink Reply by Danny Boyes on April 23, 2014 at 3:04am

Hi Seb,

True/False will give you the ability to [Dispatch] your curves to different "commands" within Grasshopper.

If you need to maintain the data Structure then <Grafting> the list will allow you to [Merge] them back latter in the same order

Or am I still missing the point?

Permalink Reply by Seb on April 23, 2014 at 3:27am

i think we are getting a lot closer but im still getting errors...

i cleaned up my files and here they are... maybe you see somethings i dont...

thanks a lot Danny

Attachments:

• test.3dm, 156 KB
• test.gh, 22 KB

Permalink Reply by Danny Boyes on April 23, 2014 at 4:05am

This would be my method:

1) Combine all the matching curves on separate branches.

2) Then [Cull Pattern] based on [Closed]

3) with the pairs of curves or boundary curves that remain create a [Boundary] surface

Attachments:

• db_Method.gh, 30 KB

Permalink Reply by Danny Boyes on April 23, 2014 at 4:23am

Also I note from the image I posted above you use the output of a panel. This is not a Number it is Formatted Text and GH needs to convert this back to being a number for [Multiply]. This does two things, introduces rounding and also overhead in calculation. In this case its minuscule amounts of time and the accuracy/order of the values is not needed but you should be aware that it occurs in case you start using thousands of values and depend on greater precision.

Primarily use [Panels] to either input or display values. There are occasions when you require values to be converted to text, in which case I would use a [Text] param. This again reduces the overhead because GH doesn't have to populate the [Panel] for you to read.

Permalink Reply by Seb on April 23, 2014 at 9:12pm

yea.....I knew I was too soon and too fast in the process... This works better...

Thanks very much Danny! I appreciate it!

Permalink Reply by Seb on April 23, 2014 at 10:33pm

Hi Danny,

However there seems to be some closed planar curves that are being ignored or skipped. This become apparent when i more around the attractor point. It feels like there is a tolerance level somewhere that can be adjusted....

Any clue on whats going on?

Cheer

Permalink Reply by Danny Boyes on April 24, 2014 at 2:56am

I noticed a few that seemed out of place, but I think this is due to the curved surface and the location of your Attractor point making them closer than the ones which "appear" closer

Maybe a better approach would be to find the Closest Point on the Surface of your attractor and then calculate from there