modeling with force and attractor

Replies to This Discussion

Permalink Reply by peter fotiadis on February 20, 2015 at 2:50am

Hmm ...

(You tube it doesn't work right in my workstation: no idea why)

1. You want to "influence" something (for instance: control points that make a nurbs) with something else (points [i.e. "attractors"], surfaces [i.e. collections of "attractors" derived by a variety of ways out of surfaces], whatever) right?

2. If so I had at least 20 "similar" test cases made long time ago but due to a major reconstruction ... I've replaced all with C# code (and being idiot I've deleted the old defs), thus maybe these are not suitable for you (or maybe you are familiar with C#?).

3. I'll prepare something "simple" for you soon.

In the mean time get these old defs that mysteriously survived from the massacre, he he (not matching 100% your request - but good to have them anyway, I believe).

best, Peter

Attachments:

• Attr_Pts_VS_surfaces_V2.gh, 56 KB
• Spatial_V5A.gh, 18 KB
• gills5.gh, 389 KB

Permalink Reply by pirooz on February 20, 2015 at 4:53am

HI Peter

sample 3 is very very helpful

thanks alot boy

best regard, pirooz

Permalink Reply by peter fotiadis on February 20, 2015 at 6:25am

I haven't found (yet) time (that @#@$ practice of mine == awful^^N) to do something 100% suitable for you but I think that pretty soon your specific case could be ready (I'm starting(?) right(?) now(?) - God/practice permit, he he). I do hope that you won't mind a very smallish piece of C# code among classic GH components: just to speed "development" time a bit, he he.

more soon

Permalink Reply by peter fotiadis on February 20, 2015 at 8:20am

OK, get this that I believe that is what you asked for : a collection of attractors (that define a surface - but can being derived from it by "inverting" what came from where) that push/pull a surface.  Sorry about the code part (you can do it with standard components as well) but I had really a very limited time to do this demo case. Maybe I'll convert the C# to components later.

PS: added some options more in Case1.

PS: all test data are internalized (but load Rhino file first: GH frequently fails to memorize internalized data).

best, Peter

Attachments:

• Spatial_V5B.gh, 369 KB
• Spatial_V5B.3dm, 965 KB

Permalink Reply by pirooz on February 20, 2015 at 9:14am

Thaaaaaaaaaaaaaaaaaaaaaaaaanks Peter 

Permalink Reply by peter fotiadis on February 20, 2015 at 9:48am

No ... you should sue me instead (WHAT I was thinking? apparently nothing, he he).

GIANT bug detected (dist = 1/dist * factor instead of dist *= whatever).

Please accept my apologies, best, Peter

Attachments:

• Spatial_V5C.gh, 378 KB