8000 FlahaGrow/docs at main · rafatahmed/FlahaGrow · GitHub
[go: up one dir, main page]

Skip to content

Latest commit

 

History

History

docs

README.md

FlahaGrow documentation

This documentation describes the repository as implemented. Source code is the authority when a document and code disagree. FlahaGrow is a Windows Rhino 8 / Grasshopper add-on (net7.0-windows) for Radiance-oriented greenhouse-lighting workflows; it is not a general Honeybee or Ladybug integration.

Read in this order

  1. System architecture — assemblies, assets, external programs, and ownership boundaries.
  2. Radiance methods — the implemented climate-based matrix calculation and the lux-to-PPFD/DLI boundary.
  3. Scientific PPFD/DLI assessment — reliability limits and enhancement roadmap.
  4. Setup — project contexts, assets, and Radiance readiness checks.
  5. Annual daylight workflow — manifest-backed annual results and the cache contract.
  6. Electric-light workflow — IES conversion, electric annual runs, and composition.
  7. Complete component reference — all 30 components by category, exact ports, defaults, units, wiring, workflow and revisions; toolbar navigation provides the short overview.
  8. Validation and plugin audit — automated checks, cleanup scope and remaining host/reference acceptance.

Documentation rules

Recommended current wiring: Loaded Result → inherited weather → automatic plot attributes. This supersedes manual UTC entry and manual reconstruction of plot titles/units.

Implemented scalar pathway: Plant-light workflow and component migration lists new and modified components, exact wiring, compatibility rules and open acceptance gates. The task plan also includes remaining, unimplemented work.

Research evidence: Daylight, LED and horticultural spectral profiles contains the deeper scientific report, original datasets, reproducible calculations and proposed profile contract. Core embeds the CIE photopic weighting data; 18 reference source profiles are available through the Spectral Profile table, with explicit limitations acknowledgment; they are not certified fixture presets.

  • Document observable inputs, outputs, units, files, ownership, and failures.
  • Use the plugin audit for current evidence; approved obsolete archive documents have been removed.
  • Update docs and tests whenever a component contract, manifest, cache format, or tool requirement changes.
0