API field
Device types
The rack, tracker and east-west ridge sizes placed in the scene, one to ten
What it is
A device type is one size of fixed rack, single-axis tracker or east-west ridge: its kind, its length and width, the modules and strings it carries, and the border of structure around its modules. Every placement names a type by its id.
Typical values and how to get it
One type per rack or tracker size: two or three for fixed racks, up to four for a tracker system. On a roof, one type per rectangular array when no object shades part of it. Use a one-module type placed once per module where the modules do not form a rectangle or an object shades part of the array: with row-to-row shading off, each placement sees the objects from its centre only, so one placement per module resolves a shadow across the array, as the residential example does. Fixed racks and trackers mix freely in one scene. Ids are unique, 1 to 64 characters. Up to ten types; a type no placement uses raises a warning from POST /api/scene/validate.
An ewf type is one east-west ridge: two faces back to back at the face tilt. width is one face's slant width and gap the distance between the two faces' top edges. modules and strings count both faces and are even numbers. Place the ridge at its centre, at the height of the top edges, with azimuth_deg along the ridge (180 for a north–south ridge, whose faces look east and west) and tilt_deg the face tilt. The engine turns each ridge into two fixed faces, <id>.e facing azimuth − 90 and <id>.w facing azimuth + 90, each with half the modules. East-west ridges take a scene of their own: ewf types do not share a scene with gft or sat types, and they need array.track_mode ewf. GET /api/scene-examples/east_west is an example scene, and the guide page east_west gives the run request around it.
API
scene.types