Coffee + Grasshopper

A daily geometric problem is presented to the grasshopper 3d community. Degrees of difficulty vary by day.

The idea is to sharpen skills, challenge, or a fun exercise: Useful for beginners wanting to learn, or as an alternative to your morning coffee + cross-word puzzle. 

Rules:

Contributions can be posted by anyone. Either selected from a previously posted problem from the general discussion (please acknowledge original poster), a selection from one of the many grasshopper+ primers (please include credits) something you think is fun, curious about, or even something you want to learn.

We should keep the entries dated so we can track them. One new problem per day (so if you see one posted for today- there is always tomorrow).

User(you) adds post titled: date-name of problem.

 

Solutions will be posted with breakdowns, either in logic procedure, etc. And in the spirit of the NY Times, an explained solution will be posted as well within the following days.

Remember there are multiple ways to solve a problem- however the “official” post should include a “clean and elegant” (or simplest) solution. So that all learning can develop better scripting habits.

Rules: an explanation.

1- Submission categories are as follows: 

Native 

Plug In

Scripted

Each category should have a difficulty rating - 1 to 5 perhaps. 

They should be included in title for clarity-

Date_NameOfProblem_Native Plugin or Script_Difficulty

2. Since we are an international community, and this is an open group- a C+G day starts at the time of 10 am local poster’s time.

3.Anyone can set the next question. However the same person cannot set two days in a row. If a question is up- then next person needs to wait until the following day to post. You can PM Danny Boyes or Myself (Monique) if you are having posting issues- (i.e.: how to post, or have been trying to post, but keep missing the opportunity) 

4. Answers are presented in the typical grasshopper community response way: in the form of examples, and/or screen shots. For screen shots: make sure the nodes are legible, if you do a function inside a node make sure we can see what you did. Verbal explanation. Maybe picture of result.

The difference between this group and the general discussion is that the poster should know how to solve the problem, be able to post a solution up themselves.

5. The poster judges the answer. They should offer a sample solution as well when they declare the winner.

However overall quality control may be checked by moderators of the group.

6. Still thinking about this one. 

[Utilities Series] May 11, 2014 - Panelling machines.

As easy as it sounds. David R. proposed some days ago to search for neat and clean solutions for common and simple problems that everybody could understand. I've tagged this c+GH post as "Utilities series", but it could be changed in the future with nicer and more interesting names.

It's perfectly known that lot of plugins has been released to empower GH panelling capabilities, but usually lightweight and native systems could be required to accomplish specific little (or big) design tasks. In addition to this, the panelling process is a task that let the user to play and learn and practice deeply concepts about surface/meshes topology, list and data trees management, etc. So I though that this could be a perfect starting point for the "Utilities series" in c+GH.

To open this group of c+GH post I will start with something simple that everyone that have used GH has tried sooner or later in his/her learning process: how to panel a surface using standard/built-in GH components only.

Topics that could be covered (aka, problem categories):

  • Planar panels. 
  • Curved panels. 
  • Mixed solutions: curvature/distortion triggers or limits.

Given a NURBS surface, create a single panelling system that implement one of the categories described for only one kind of panel (triangular, quadrilateral, n-gon). Of course, curved panels are not compatible with triangular shapes, etc,  so try to pick a compatible combination.

Further considerations:

  • The implemented solution should let the user to interact with every panel easily, so the proposed algorithm should track the panellization process avoiding to destroy helpful information/data structures for further modifications in the panelling system.
  • NURBS and mesh solutions are both allowed.
  • None, plugin or scripted component allowed.
  • The cleanest, shorter and less processing-time-expensive solution in every category will be the winner (please, consider using profiler intensively).
  • Deadline: May 18, 2014.
  • up

    Daniel Piker

    Hi Angel,

    I think it would be great to have some more discussion of panelling, but this is a huge topic and that problem description is rather nebulous.

    Perhaps it could lead to more useful discussion if a clear question is asked.

    1
    • up

      Scott Ward

      I do Local SEO for Cannabis Business at https://mjseo.agency/local-seo/. Neighborhood SEO it is a magnificent chance for organizations in the pot business inside one locale to rival huge associations that work all through the country. Because of nearby SEO, clients will find your site at the most elevated mark of the Google. In the event that you want to notice weed things in some ?ity, the most significant positions will be involved by the destinations of the cannabis shops of this city.