Rhino/GH - Ladybug Expert

announcements jobs
1

Seeking a Rhino Grasshopper expert to simulate bioclimatic design interventions at multiple architectural and urban scales. The role involves using Ladybug Tools, Honeybee, Butterfly, and Dragonfly to analyze/optimize proposed buildings and masterplans. We are an architecture and urban research studio that develops workflows for our design-build projects and speculative interventions.

  1. Executive Summary & Objective

This document outlines the implementation framework for an advanced, 100% open-source environmental simulation workflow inside Rhino and Grasshopper. By standardizing on Ladybug Tools, our studio will build critical in-house computational engineering skills, and achieve seamless scalability from single-family passive residential projects to massive urban masterplans.

Our immediate objective is to apply this workflow to the current residential project to validate fully passive strategies (no mechanical HVAC systems) requested by the client. We will specifically simulate a custom roof airscoop, glass block wall thermal/glazing performance, and the dynamic thermal battery behavior of concrete walls and radiant floors.

2. Core Software Ecosystem & IT Pre-Requisites

To execute this workflow, the IT department must install the following software packages on all team workstations. These core simulation engines run silently in the background, controlled directly through our Grasshopper canvas.

  • Rhino 8 (or current studio standard): The foundational 3D modeling platform.

  • Ladybug Tools (Core Core Engine): The primary Grasshopper plugin interface connecting Rhino to external engines.

  • EnergyPlus (v24.1+): The U.S. Department of Energy’s flagship thermal simulation engine. Handles thermal mass, hourly comfort, and passive heat migration.

  • OpenFOAM (v10 or current compatible OpenFOAM-Windows variant): The specialized Computational Fluid Dynamics (CFD) engine. Handles wind aerodynamics and 3D air velocity tracking.

  • Radiance (v5.4+): The ray-tracing engine. Handles highly precise daylighting and annual solar exposure calculations.

  • URBANopt / Urban Weather Generator (UWG): Sub-engines utilized by Dragonfly for district-scale heating/cooling and Urban Heat Island calculations.

3. Workflow Architecture

The entire environmental analysis pipeline is divided across four specialized Grasshopper sub-plugins, running on a singular data thread:

                        ┌─────────────────────────────────────────┐
                        │       Rhino / Grasshopper Geometry      │
                        └────────────────────┬────────────────────┘
                                             │
      ┌──────────────────────────────────────┴──────────────────────────────────────┐
      ▼                                      ▼                                      ▼
┌──────────────────────────┐           ┌──────────────────────────┐           ┌──────────────────────────┐
│        HONEYBEE          │           │        BUTTERFLY         │           │        DRAGONFLY         │
├──────────────────────────┤           ├──────────────────────────┤           ├──────────────────────────┤
│ Engine: EnergyPlus       │           │ Engine: OpenFOAM         │           │ Engine: URBANopt         │
│ • Concrete Thermal Mass  │           │ • Roof Airscoop CFD      │           │ • District Energy Systems│
│ • Glass Block U-Values   │           │ • Air Velocity Vectors   │           │ • Urban Microclimates    │
│ • Radiant Slab Loops     │           │ • Pressure Coefficients  │           │ • Macro-Scale Massing    │
└──────────────────────────┘           └──────────────────────────┘           └──────────────────────────┘

4. Phased Project Deliverables

Phase 1: Conceptual Design & Climate Contextualization

Objective: Establish environmental boundary conditions and script the parametric geometry for the passive roof feature.

  • Deliverable 1.1: Microclimate Data Assessment (Ladybug Core)

    • Action: Download and ingest the local .epw weather file into the Grasshopper canvas.

    • Output: Dynamic Wind Rose diagrams mapping seasonal prevailing winds, psychrometric charts identifying natural ventilation opportunities, and a clear breakdown of the exact calendar weeks where the roof scoop must drive passive cooling.

  • Deliverable 1.2: Parametric Airscoop Scripting (Native GH + Ladybug)

    • Action: Construct a Grasshopper definition utilizing geometric sliders to alter the roof airscoop’s aperture surface area, catch angle, and directional orientation vector.

    • Output: An adaptable, parametric roof geometry capable of shifting form based on real-time climate inputs.

Phase 2: Design Development & High-Fidelity Validation

Objective: Construct custom material assemblies, simulate 3D aerodynamic airflow, and validate multi-zone annual passive comfort.

  • Deliverable 2.1: Advanced Material Construction Matrices (Honeybee)

    • Action: Use Honeybee’s Opaque Construction component to design the multi-layered concrete wall and floor assemblies (defining precise material thickness, density, and thermal conductivity). Use the Window Construction component to manually script the unique center-of-glass U-value, solar heat gain coefficient (SHGC), and frame dimensions specific to our chosen glass block product.

    • Output: Custom Honeybee material libraries tailored specifically to our architectural specifications.

  • Deliverable 2.2: Aerodynamic Aeration CFD Profiles (Butterfly / OpenFOAM)

    • Action: Isolate the building shell and roof scoop geometry. Establish a 3D virtual wind tunnel mesh using OpenFOAM via Butterfly. Run a steady-state CFD simulation under dominant local wind directions.

    • Output: High-resolution 3D streamline visualization maps and air velocity vector diagrams illustrating exactly how wind pressure drives outdoor air down into the living spaces.

  • Deliverable 2.3: Closed-Loop Annual Comfort Validation (Honeybee AirflowNetwork)

    • Action: Extract the wind pressure coefficients (\(C_{p}\) values) calculated by Butterfly. Link them directly back into Honeybee’s EnergyPlus AirflowNetwork components. Disable all mechanical HVAC settings to simulate a 100% un-mechanized environment.

    • Output: An annual hourly simulation mapping Spatial Thermal Comfort (PMV/PPD metrics). This will verify the exact indoor temperature ranges and prove structural comfort compliance across every square foot of the floor plate during extreme summer and winter peaks.

Phase 3: Urban-Scale Project Scaling (Dragonfly Integration)

Objective: Scale our in-house capabilities from single-family residential up to multi-block urban masterplans without overloading hardware memory.

  • Deliverable 3.1: Macro-Zoning & Massing Automation (Dragonfly)

    • Action: Transition the computational logic from Honeybee to Dragonfly. Implement Grasshopper text-sorting rules to read raw Rhino layer names (e.g., LAYER: Site_Zone_Retail_01) to automatically assign thermal characteristics, occupancy schedules, and programmatic load properties to entire city blocks simultaneously.

    • Output: A high-speed macro-scale urban energy baseline model.

  • Deliverable 3.2: Urban Heat Island (UHI) Microclimate Profiling

    • Action: Interface Dragonfly with the Urban Weather Generator (UWG) to mathematically alter the regional rural .epw climate file. This must account for how city geometry, asphalt mass, concrete structures, and lack of vegetation distort local ambient air temperatures.

    • Output: Microclimate temperature adjustment profiles detailing urban-scale heat gains, paving material performance, and pedestrian plaza thermal comfort maps.

  • Deliverable 3.3: District Energy & Infrastructure Mapping

    • Action: Connect the urban model to URBANopt to evaluate shared centralized solar grids, district heating/cooling infrastructure loops, and regional energy load balancing.

    • Output: Macro-scale district infrastructure energy consumption matrices and masterplan sustainability performance reports.

5. Team Execution Strategy

To roll this workflow out effectively, our computational design leads should structure the file system using a unified Rhino layer naming convention (e.g., HB_Opaque_ConcreteFloor, HB_Glazing_GlassBlock). This will allow Grasshopper scripts to automatically filter, read, and assign simulation attributes across all future projects.

2 Likes