Photographing Steven Holl’s Chapel of St. Ignatius: An AI Consultant’s Guide

Capture Protocol: Volume-by-Volume Bracketing

Steven Holl’s Chapel of St. Ignatius at Seattle University is not a single photographic subject—it is seven distinct light volumes, each with its own exposure demands. Most AI consultants treat architectural capture as a data-collection problem solvable by one HDR pass, but this building breaks that workflow: the steel-and-glass contrast in the light slots and the deep concrete shadows in the narthex require a volume-by-volume bracketing strategy before any AI pipeline can produce reliable results. This guide moves from capture protocol (exposure bracketing per light volume) to AI processing (photogrammetry, semantic segmentation, NeRF training) to validation (daylight factor analysis against Holl’s design intent), with a case study comparing three reconstruction pipelines.

Capture Protocol: Volume-by-Volume Bracketing

The single most common failure in AI-driven architectural analysis of the Chapel of St. Ignatius is not poor photogrammetry or weak model training—it is a capture protocol that treats the interior as one light zone. Steven Holl’s seven “bottles of light” each produce a distinct luminance range, and a single exposure setting guarantees blown highlights in the blue stained-glass volumes and crushed shadows in the concrete-and-steel zones. The fix is volume-by-volume bracketing at ±2 EV per zone, with white balance locked per volume rather than set globally. According to ArchDaily’s documentation of the chapel, the seven light volumes are geometrically distinct, and the luminance delta between a cool blue-glass volume and a warm concrete volume can exceed 6 EV—beyond what any single HDR bracket can recover.

Set white balance per volume zone, not per scene. Warm reflected light off concrete and steel measures approximately 5600K; cool transmitted light through the blue stained glass measures approximately 3200K. A single white balance setting across all seven volumes will produce unrecoverable color shifts that confuse AI luminance models. One practitioner on Reddit described spending three days retraining a daylight-factor classifier only to discover that the training data had been shot at auto white balance, introducing a 1500K swing between frames.

Overexposed highlights in stained-glass windows are the most common error degrading AI luminance analysis. Shooting RAW is mandatory, but the recovery tool matters. Capture One’s “Highlight” tool recovers up to 2 stops of detail in the blue-glass volumes without introducing color artifacts; Lightroom’s default highlight slider clips faster and produces a magenta shift that propagates through semantic segmentation models. One r/archviz user reported that shooting at f/8 with ISO 100 and a tripod produced consistent sharpness across the steel structure, but the blue glass volumes required shutter speeds 2–3 stops slower to avoid underexposure—a tradeoff that demands per-volume metering rather than a single evaluative meter reading.

Auto-exposure bracketing without locking white balance is a trap. The camera will shift color temperature between brackets to compensate for perceived neutrality, creating a dataset where the same concrete surface appears at 4800K in one frame and 6200K in the next.

Edge case: if the chapel is in use during services, you cannot control ambient lighting. Schedule capture during overcast midday (11:00–14:00) when the light volumes are most diffuse and least variable. Overcast conditions reduce the luminance range between volumes from approximately 6 EV to 3 EV, making a single ±1 EV bracket viable for the entire interior. This is the only scenario where a global exposure strategy works. For all other conditions, shoot each volume as a separate sequence: meter the brightest highlight in the glass, set exposure for that zone, bracket ±2 EV, then move to the next volume. The resulting dataset will contain 7–14 distinct exposure groups, each with consistent white balance and tonal range—ready for photogrammetry, semantic segmentation, or NeRF training without color-correction overhead.

Actionable step: before your next shoot, create a volume map of the chapel interior with seven labeled zones. For each zone, record the metered exposure for the brightest highlight and the white balance reading from a gray card. Shoot one ColorChecker frame per zone, then execute the ±2 EV bracket sequence. This protocol adds approximately 20 minutes to the capture session but eliminates the most common cause of AI model failure in architectural analysis.

Photogrammetry: Overlap Rules for Curved Concrete

For sub-centimeter accuracy on the Chapel of St. Ignatius, COLMAP’s FAQ derives these numbers from the ETH3D multi-view stereo benchmark, which tests on planar and textured surfaces. Curved concrete and the chapel’s seven distinct light volumes demand a tighter protocol: shoot each “bottle of light” as a separate capture sequence, maintaining the overlap ratios within each volume, not across the entire interior. One r/photogrammetry thread reports that practitioners who shoot the whole nave in a single pass lose alignment on the curved east wall because the luminance gradient between Holl’s blue-stained-glass volume and the adjacent concrete column confuses feature matching.

Shoot on an overcast day or use a polarizing filter. Direct sunlight creates harsh shadows that shift between frames as the sun moves, breaking the temporal consistency required for photogrammetry. The chapel’s east-facing stained glass is particularly problematic in morning light—shadow edges move up to 10 cm per hour, which is enough to degrade alignment across a 30-minute capture session. As detailed in the Capture Protocol: Volume-by-Volume Bracketing section, include a color calibration target, such as an X-Rite ColorChecker, in at least 5% of frames.

Photogrammetry is preferred over LiDAR for this interior because structured-light scans produce fewer specular reflections on the chapel’s glass and polished concrete surfaces, according to Autodesk’s comparison guide. LiDAR excels on large-scale exterior massing but struggles with the mixed-material interior where glass, steel, and concrete meet. Typical deviations on curved surfaces fall between 1 cm and 3 cm, per CloudCompare documentation; deviations above 5 cm indicate a capture or alignment failure that requires re-shooting the affected volume.

Actionable step: before your next capture session, generate a ChArUco board using OpenCV’s cv2.aruco.CharucoBoard_create function, print it at A3 size, and place it at 2-meter intervals along the chapel’s concrete columns.

Semantic Segmentation: Material Classification from 200 Images

Semantic segmentation of architectural materials in the Chapel of St. Ignatius fails when models trained on outdoor scenes encounter the interior’s blue stained glass, which is routinely misclassified as “sky.” One r/computervision user reported that retraining with just 20–30 interior-specific glass images resolves this error entirely. A pre-trained DeepLabV3+ model on a custom dataset of 200–300 labeled images can achieve ~85% mean Intersection over Union (mIoU) on concrete, glass, and copper facades, according to Papers with Code benchmarks. That baseline is sufficient for rough material maps but not for the precision required in daylight factor analysis or BIM integration.

The jump matters because misclassifying a copper roof element as “wood” introduces false thermal and reflectance values into downstream simulations. Copper surfaces reflect warm tones that confuse classifiers trained on generic metal; include at least 10 copper-specific images in the training set to avoid this false positive.

Annotation tools matter for consistency. Use LabelMe or CVAT for polygon-based labeling; budget 4–6 hours for 200 images with 4 material classes, assuming a single annotator. This enables annual daylight factor analysis and seasonal solar gain simulation directly in Autodesk Revit, without manual redrawing of material boundaries. One practitioner on Reddit noted that exporting masks as 8-bit PNGs with class IDs mapped to Revit material parameters saves roughly 10 hours per project compared to manual polygon tracing in the BIM environment.

Edge case: the chapel’s concrete walls contain subtle color variations from the light volumes, which can cause a model to split a single wall into multiple material classes. A single annotator using consistent labeling guidelines—concrete includes all poured-in-place surfaces regardless of shadow—prevents this fragmentation. Do not rely on AI-based auto-labeling tools for the initial dataset; they introduce class confusion that propagates through fine-tuning. Manual annotation of the first 200 images, followed by model-assisted labeling for expansion, produces cleaner training sets.

Actionable step: download a pre-trained DeepLabV3+ from PyTorch Hub, annotate 50 images per material class, and fine-tune for 20 epochs to achieve production-ready segmentation accuracy.

Neural Radiance Fields: Novel Viewpoints Under Uniform Light

Neural radiance fields promise novel viewpoints from a sparse photo set, but the Chapel of St. Ignatius exposes their fundamental weakness: NeRFs treat light as geometry. When the seven “bottles of light” create non-uniform illumination, the model interprets shifting shadows and color temperatures as physical surfaces, producing floating artifacts in light-well areas. One r/NeRF user reported that the chapel’s blue glass volumes generated ghostly semi-transparent planes in novel views because the network could not distinguish between transmitted blue light and a blue-painted wall. The fix is not algorithmic—it is capture discipline.

According to Matthew Tancik’s original NeRF paper, training on 100–150 interior and exterior photos can generate convincing walkthroughs, but only under uniform lighting. For this chapel, that means capturing all photos within a single 2-hour window on an overcast day. Cloud cover acts as a giant diffuser, flattening the dynamic range between the altar’s direct light slot and the narthex’s indirect glow. Shoot outside that window and the model will interpolate between sunny and overcast conditions, producing blurry results in the transition zones. Practitioners on Reddit confirm that even a 30-minute gap between capture batches introduces visible ghosting in the final render.

For faster iteration, use instant-ngp (NVIDIA’s implementation) rather than the original NeRF codebase. Training drops from hours to roughly 10 minutes on an RTX 4090. The tradeoff is lower quality on specular surfaces—the chapel’s steel beams and copper details will appear softer. If those elements are critical for the client walkthrough, fall back to the original NeRF with positional encoding tuned for high-frequency details. One architectural visualization firm reported that instant-ngp’s hash-grid encoding struggled with the copper wall panels near the confessional, producing a metallic sheen that flickered between frames.

A specific failure mode deserves attention: the blue stained-glass volumes. NeRF models trained on standard 8-bit JPEGs cannot resolve the difference between transmitted light and surface albedo in these zones. The Ref-NeRF extension (from the same research group) addresses this by modeling outgoing radiance as a function of surface normal and view direction, but it requires HDR training images. For the chapel, this means bracketing the light-well shots at ±2 EV and merging to HDR before feeding the pipeline—a step most consultants skip, then wonder why the altar window looks like a white void.

Export the trained NeRF as a mesh via Nerf2Mesh for import into BIM software. Expect metric accuracy of ±5 cm—sufficient for visualization and client presentations but inadequate for structural analysis or retrofit planning. The mesh will capture the volumetric feel of the light wells but will smooth over the sharp edges of the concrete pours. Verify the export against the photogrammetry model from the earlier section; if the NeRF mesh deviates by more than 10 cm at any control point, re-train with additional HDR frames from that zone. A concrete next step: before your next shoot, set a calendar reminder to check the local cloud forecast for the 2-hour window, and pack a polarizing filter for the blue glass volumes—it reduces the floating-artifact problem by cutting scattered light at the capture stage.

Case Study: Three Reconstruction Pipelines Compared

For metric-grade architectural reconstruction, the choice between photogrammetry, LiDAR, and NeRF is not a matter of preference but of tolerance for specific failure modes. The Chapel of St. Ignatius exposes these tradeoffs sharply because its curved concrete surfaces, stained glass, and seven distinct light volumes each break different capture methods. A practitioner who selects the wrong pipeline for the intended output—structural deviation analysis versus client walkthrough—will waste hours on data that cannot answer the question.

Option A, photogrammetry with COLMAP, delivers the best balance of cost and metric accuracy for interior analysis. This is sufficient for CloudCompare deviation analysis to verify that Holl’s poured-in-place concrete matches the design intent within construction tolerances. The total time is nine hours: three on site, six processing on a workstation with an RTX 4090 and 64 GB RAM. The cost is effectively zero beyond the camera and the operator’s time, since COLMAP is open-source. The failure mode is specular surfaces: the stained glass windows produce featureless white regions that fail to match across frames, creating holes in the mesh that require manual cleanup.

Option B, a structured-light scanner such as the Artec Leo, achieves ±2 mm accuracy on the curved concrete walls—roughly four times better than photogrammetry. The capture takes one hour, and processing requires two hours in the vendor’s proprietary software. LiDAR is the correct choice only when the primary deliverable is the concrete massing and the glass surfaces are treated as secondary.

Option C, a NeRF trained with instant-ngp on 120 photos captured within a two-hour overcast window, produces visually compelling novel viewpoints for client walkthroughs. Training takes ten minutes on an RTX 4090. The metric accuracy, however, is ±4 cm—an order of magnitude worse than LiDAR and five times worse than photogrammetry. This is insufficient for structural analysis or daylight factor validation against Holl’s design intent. The NeRF is useful only for presentations where the client needs to see the space from angles that were not physically captured. The edge case that kills NeRF entirely is renovation scaffolding: the occlusions confuse the neural network, producing floating artifacts that no amount of post-processing can fix.

The decision rule is straightforward. Use photogrammetry when the deliverable requires metric accuracy below 1 cm and the budget is under $200. Use LiDAR when the primary geometry is concrete or stone and the client will pay for sub-millimeter precision on massing. Use NeRF only for visual walkthroughs where the client explicitly accepts that the model is not dimensionally accurate. One r/photogrammetry user combined COLMAP’s dense point cloud as input to instant-ngp, achieving both metric accuracy and visual quality, but this required 200+ photos and eight hours of processing—a hybrid pipeline that is viable only for flagship projects with a dedicated operator.

Take the chapel’s floor plan and mark each of the seven light volumes. For each volume, decide whether the primary deliverable is a deviation report against CAD or a client-facing animation. That decision dictates the pipeline, the capture time, and the budget. Do not let the visual appeal of NeRF walkthroughs override the metric requirements of the structural analysis.

Validation: Daylight Factor Analysis Against Holl’s Intent

CloudCompare’s “Cloud-to-Mesh” distance tool is the standard method for comparing the as-built photogrammetry model against Steven Holl’s original CAD drawings. Typical deviations on the curved concrete surfaces fall between 1 cm and 3 cm, which reflects construction fidelity within normal tolerances for cast-in-place concrete. If the deviation exceeds 3 cm on a light-well edge, the daylight factor simulation will produce inaccurate results because the geometry no longer matches the designed aperture. One r/architecture thread notes that practitioners often skip this step and rely on visual inspection, which misses sub-centimeter shifts that propagate through the annual solar gain calculation.

AI-generated depth maps from single photos, using MiDaS v3.1, can be integrated into a real-time spatial analysis dashboard via Python and Open3D. This enables contrast-ratio visualization of the light wells without building a full photogrammetry model. However, MiDaS struggles with the chapel’s non-uniform lighting—the mixed-color-temperature zones from the blue stained glass and warm copper surfaces confuse its monocular depth estimation. Field threads report that MiDaS produces depth artifacts in the nave where the daylight factor drops below 2%, making it unreliable for quantitative validation. Use MiDaS only for preliminary spatial sketches, not for final daylight factor analysis.

The primary failure mode in this validation workflow is holes in the photogrammetry model at the light-well areas, caused by the high contrast between the bright glass and dark concrete interior. If the model has holes, the daylight factor simulation will produce false low values because the simulation software treats missing geometry as opaque surfaces. Fill these holes using Poisson surface reconstruction in CloudCompare before exporting to Revit. If the deviation exceeds 3 cm on a light-well edge, the daylight factor simulation will produce inaccurate results because the geometry no longer matches the designed aperture. One r/architecture thread notes that practitioners often skip this step and rely on visual inspection, which misses sub-centimeter shifts that propagate through the annual solar gain calculation.

What to do next

This guide has outlined a technical workflow for capturing Steven Holl’s Chapel of St. Ignatius in a form suitable for AI-based architectural analysis. To apply these methods to your own project, begin by validating your equipment setup against the documented capture protocols, then proceed with a structured field test.

Also worth reading: The Art Book Collector's Guide to Authentication Spotting First Editions and Limited Prints · Decoding Mattress Firmness A Guide for Sleepers of All Sizes in 2024 · Mastering the French Pronunciation of Le Corbusier A Guide for Architecture Enthusiasts · T-Mobile Arena's Location Guide Finding Your Way to Vegas' Premier Entertainment Venue on The Strip

Sources: seattleu, wikipedia, slideshare, architectmagazine, tumblr