{"id":290,"date":"2025-08-17T13:22:41","date_gmt":"2025-08-17T17:22:41","guid":{"rendered":"https:\/\/tabeertariq.com\/?page_id=290"},"modified":"2025-08-25T22:12:06","modified_gmt":"2025-08-26T02:12:06","slug":"rippled-logics","status":"publish","type":"page","link":"https:\/\/tabeertariq.com\/?page_id=290","title":{"rendered":"Rippled Logics"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\n

Computational waves shaping immersive form.<\/p>\n<\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

Challenge<\/h2>\n\n\n\n
\n

For the VRT building we were asked to design a parametric ceiling for the auditorium. The auditoriums ceiling was medium height and had structural beams and lights running under the upper slab. The aim was to develop an acoustic panalled ceiling which would span through the auditiorium maintaining a sufficient clear height, adding volume and depth to the space and hiding the structure above and be manufacturable. Instead of modeling everything manually in Revit, we used Rhino.Inside Revit<\/strong> so we could pull the auditorium geometry directly into Grasshopper. This gave us control over ripple logic, let us test multiple iterations, and made it easier to adjust the design live with the team. Material fabrication acquired from a separate vendor.<\/p>\n<\/blockquote>\n\n\n\n

\n
<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n\n

Process<\/h2>\n\n\n\n
\n

Design rule<\/strong>: The pattern of the ripple needs to be kept in mind. Its origin and focal point and thus its propagation towards the outside. The cieling had subtle and gradual holding volume and depth however maintaining a natural path of eye movement towards the audience. It should not break the flow and movement. A minimum clearance should be maintained.<\/p>\n<\/blockquote>\n\n\n\n

\n
\n

Matrix<\/em><\/h2>\n\n\n\n
    \n
  1. Ceiling corresponds to auditorium boundary imported from Revit.<\/li>\n\n\n\n
  2. Ripple originates at focal point above stage with strongest amplitude at origin and then fading outward.<\/li>\n\n\n\n
  3. Maintain a minimum head clearance for audience seating.<\/li>\n\n\n\n
  4. Account for service interruptions (structural beams, lighting).<\/li>\n\n\n\n
  5. Panels must be cleanly subdivided for fabrication.<\/li>\n\n\n\n
  6. Workflow remains connected to Revit for coordination purposes.<\/li>\n<\/ol>\n<\/div>\n\n\n\n
    \n

    Features<\/em><\/h2>\n\n\n\n
      \n
    1. Explored multiple ripple logics such as single, rotated, merged Also experimented with intersecting ripples<\/li>\n\n\n\n
    2. Make amplitude, frequency, and fade values to be adjustable.<\/li>\n\n\n\n
    3. Creating masking around structural beams and lights.<\/li>\n\n\n\n
    4. Produce a clear panelization logic for accurate customization. .<\/li>\n\n\n\n
    5. Maintain a Direct Grasshopper to Revit link so design updates stay live.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n\n\n\n
      \n

      The workflow was built in steps. First ripple generation, then masking, then panelization. Each round of testing added new constraints (clearances, beams, lights) and thus the script adapted quickly. This iterative approach meant we didn\u2019t have to restart the model every time a new requirement came in.<\/p>\n<\/blockquote>\n\n\n\n

      \n
      <\/div>\n\n\n\n
      \n
      \n
      \n

      Design<\/em>:<\/h2>\n<\/div>\n<\/div>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      Process:<\/em><\/h2>\n<\/div>\n<\/div>\n\n\n\n
      \n
      \n