> For the complete documentation index, see [llms.txt](https://docs.finch3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finch3d.com/courses/finch-101/finch-101-generate-corridor.md).

# Finch 101: Generate Corridor

{% embed url="<https://www.youtube.com/watch?v=_fyksqtuT0c>" %}

### 1. Open the Floor Plate Editor

Open the **Finch Sample Project**, variant `3 Custom Core`.

#### Steps:

1. Double-click on any floor.
2. The **2D floor plate editor** opens.
3. Use the **story slider** to scroll between floors.

***

### 2. Add a Centerline (for Corridor Placement)

Finch uses a **centerline** to determine where to place corridors. This can be:

* Drawn in Rhino/Revit (before uploading), or
* Drawn directly in Finch.

To **edit or draw centerlines**:

* Select the **Edit icon**
* Click twice on an endpoint to adjust the shape
* Use the **line tool** to draw a new one if needed

**Tip**: *Dragging the entire line (instead of just an endpoint) can misalign your corridor. Always click twice on the endpoint before adjusting.*

***

### 3. Generate Corridor and Cores

With the centerline in place:

* Click on the floor plate
* Select **“Generate Unit Mix and Corridors”**

This will trigger Finch’s corridor and core algorithm.

***

### 4. Adjust Generation Parameters

Use the **left-hand panel** to guide Finch’s generation logic:

#### Stairwells (Cores)

* Set **number of stairwells** (e.g., 2–4)
* Choose **placement behavior**:
  * Place stairwells in **corners**
  * Place stairwells on **ends**

#### Egress Distances

* **Single exit max**: e.g., 18 meters
* **Multiple exits max**: e.g., 30 meters

🟢 Green = compliant\
⚪️ Grey = compliant for multiple exits\
🔴 Red = non-compliant

Finch updates the layout **in real time** as you adjust these settings.

***

### 5. Define Core Dimensions

Set the following in the **Dimensions** section:

* **Core width**
* **Core depth** (includes corridor)

Example:

* Corridor width: 2m
* Core depth: 5m\
  → Set **core depth to 7m**

Use zoom to verify visual fit with your floor plate.

***

### 6. Adjust Stairwell Attractors

Stairwell attractors define which direction your stairwells face:

* Turn on/off at**tractor arrows**
* Set them to point **inward** (e.g., toward a courtyard) or **outward** (e.g., toward a façade)

***

### 7. Pause and Apply the Plan

Once satisfied:

1. Click **Pause Iteration**
2. Click **Apply Plan**

Finch will finalize the generated corridors and stairwells **without units**, giving you flexibility to run unit mixes next.

***

### 8. Programs vs. Space Types

After applying the plan, check your **data drawers**:

* **Programs**: High-level uses (e.g., Residential, Circulation)
* **Space Types**: Specific areas (e.g., Corridors, Stairs, Elevators)

**Important**:\
\&#xNAN;*If you model cores in Rhino or Revit, be sure to **assign space types** (like corridors) so Finch can recognize them during unit generation.*

***

### Summary

You've learned how to:

* Draw and edit centerlines
* Generate stairwells and corridors
* Customize corridor placement and compliance
* Apply your floor plan without units

In the next tutorial, we’ll show you how to **generate unit mixes around your custom corridor**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.finch3d.com/courses/finch-101/finch-101-generate-corridor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.