Grasshopper

algorithmic modeling for Rhino

When I "bake" curves generated with different kinds of grids, sometimes depending on grid density or structure, result of baking causes lines to overlap.

Is there possible to remove or unify overlapping lines with grasshopper?

This needs to be done for laser cutting, so laser wont cut same area several times etc.


Views: 1269

Reply to This

Replies to This Discussion

Added 'Pipes' with diameter based on tool path length (number of segments):

Attachments:
You could bake and then "make2d" in rhino.

Helpful comment also. Thanks :)

Learned couple things today.

This is fun to watch.  A simulation of the cutting tool tracing through each tool path.  'step size' slider controls speed.

Attachments:

Fixed "flashing" (and conflicting) color problem, added 'skip pts' slider that also affects simulation speed, along with 'step size'.  Both can be adjusted while the nested Anemone loops are running.

Attachments:

Decided to apply the cutting tool simulation to the tool paths generated by 'Join' curves, mentioned earlier.  The results are VERY INTERESTING, chaotic and different from the sequential order of the Anemone loop!  And vary greatly depending on grid dimensions.

More controls (see image below):

  1. Switch between "Anemone Sequence" or "Curve Join".
  2. Set minimum and maximum radius for 'Pipes', based on tool path length.
  3. Choose the number of colors (up to the number defined, 8 in this case).  Reason for this is that adjacent paths can get the same colors depending on the number of rows and columns in the grid.
  4. 'step size' and 'skip pts' control simulation speed, as before.

Attachments:

Color patterns are cosmetic and arbitrary, yet interesting to play with.  This is an 8 X 7 grid using the "Anemone Sequence" option with six colors:

Attachments:

Here is the 25 X 11 grid in the OP, with seven colors:

By the way, you don't need to wait for the "cutting tool path simulation" to see this pattern; it is available before the nested loops start.  In re-organized code, the preview at "(1)" is static, before the simulation; it is hidden to see the simulation.  The preview at "(2)" is the simulation, which traces each tool path and then reveals each one piped.

Attachments:

Hi Joseph Oster, thank you for sharing! I used your Anemone solution for my project! :)

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

© 2019   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service