Sharing Data among Grasshoppers in Different PC's

Replies to This Discussion

Permalink Reply by Martin Dembski on September 19, 2011 at 9:35am

Hi khizer,

 

for sending simple data (numbers, strings, points) between 2 or more PC's you don't really need gHowl (but it's more advanced, maybe with gHowl you are also able to send more complex geometry between 2 definitions).

You can use the Panel to export for example txt-files, whitch would be the linking part between 2 definitions or PC's.

Then you just need to connect both PC's via a home network and then you can send the data in the txt-file between both (it's also auto-updating).

I also tried this some time ago.

 

Best,

Martin.

Permalink Reply by Khizer Ishtiaq on September 19, 2011 at 12:29pm

I was able to export text files... but how can i import them in other definition??

 

Permalink Reply by Martin Dembski on September 19, 2011 at 1:12pm

Hi khizer,

 

sry for the rough explanation.

Here is a more detailed one.

Hope this helps.

 

Best,

Martin.

Permalink Reply by Khizer Ishtiaq on September 19, 2011 at 1:42pm

Thanks alot man...this surely was great help... all i now have to do is to share the txt file on network, export from one and import in the other...

 

Can you guide me how can i export geometry???

Permalink Reply by Martin Dembski on September 19, 2011 at 4:38pm

Hi khizer,

 

to share geometry directly between 2 or more Grasshopper definitions is not possible, not really the problem is you can't see what's behind this geometry, this means if you have for example a cube and a sphere booled together you just get as an output or input from Rhino Brep, but Brep doesn't say anything about the form. Also when using gHowl you have the same problem.

But you can split the geometries in the parameters you need to rebuild it.

This means if you want to share a freeform-surface, the best way is to export uv-points. Here is a list of some ways which I've tried, how to export:

(sometimes you will need the string components and if you want to share lists of geometries then you may also need the "Weave", the "Dispatch" and the cull components if you want to work with one txt-file, but sometimes it's more usefull to work with different txt-files for each parameter)

 

strings --> strings

numbers --> numbers

(I think this is clear ;))

...

 

colors --> numbers

points --> xyz-coordinates

grid --> vertices of each grid cell

planes --> xyz- directions and center point

vectors --> starting point and end point

...

 

lines --> end points

rectangle --> dimensions and working plane

circle --> working plane/center point and radius

arc --> working plane/center point, radius and angle domain

polyline --> control points

curve --> control points

interpolated curve --> division points

(problem is the accuracy (is better with a higher amount of points))

...

 

surface --> vertices

surface --> uv-points

(problem is the accuracy again (is better with a higher amount of points))

...

 

box --> vertices

box --> dimensions and center point

sphere --> center point and radius

...

 

mesh --> vertices

custom meshs --> vertices (sometimes you also need the faces)

...

 

So in general you can say you always need to export what you need as input of the component of the geometry you want to rebuild.

 

Best,

Martin.

Permalink Reply by Khizer Ishtiaq on September 20, 2011 at 9:29am

Thanks alot Martin....:)