validate

honeybee validate

Commands for validating Honeybee objects.

honeybee validate [OPTIONS] COMMAND [ARGS]...

model

Validate all properties of a Model file against Honeybee schema.

This includes checking basic compliance with the 5 rules of honeybee geometry as well as checks for all extension attributes. The 5 rules of honeybee geometry are as follows.

  1. All Face3Ds must be planar to within the model tolerance.

  2. All Face3Ds must NOT be self-intersecting (like a bowtie shape)

  3. All children sub-faces (Apertures and Doors) must be co-planar with

    their parent Face and lie completely within its boundary.

  4. All adjacent object pairs (faces and sub-faces with a Surface boundary

    condition) must have matching areas.

  5. All Room volumes must be closed solids.

Args:
model_file: Full path to a Model JSON file.
honeybee validate model [OPTIONS] MODEL_FILE

Options

-e, --extension <extension>

Text for the name of the extension to be checked. The value input is case-insensitive such that “radiance” and “Radiance” will both result in the model being checked for validity with honeybee-radiance. This value can also be set to “All” in order to run checks for all installed extensions. Some common honeybee extension names that can be input here include: Radiance, EnergyPlus, DOE2, IES, IDAICE

Default:

'All'

--plain-text, -j, --json

Flag to note whether the output validation report should be formatted as a JSON object instead of plain text. If set to JSON, the output object will contain several attributes. The “honeybee_core” and “honeybee_schema” attributes will note the versions of these libraries used in the validation process. An attribute called “fatal_error” is a text string containing an exception if the Model failed to serialize and will be an empty string if serialization was successful. An attribute called “errors” will contain a list of JSON objects for each invalid issue found in the model. A boolean attribute called “valid” will note whether the Model is valid or not.

Default:

True

--room-overlaps

Deprecated flag used to check room collisions. Use honeybee validate room-collisions instead.

-f, --output-file <output_file>

Optional file to output the full report of the validation. By default it will be printed out to stdout

Arguments

MODEL_FILE

Required argument

room-collisions

Validate whether all Room volumes in a model are solid.

The returned result can include a list of all naked and non-manifold edges preventing closed room volumes when –json is used. This is helpful for visually identifying issues in geometry that are preventing the room volume from validating as closed.

Args:
model_file: Full path to a Honeybee Model file.
honeybee validate room-collisions [OPTIONS] MODEL_FILE

Options

--plain-text, -j, --json

Flag to note whether the output validation report should be formatted as a JSON object instead of plain text. If set to JSON, the output object will contain several attributes. An attribute called “fatal_error” is a text string containing an exception if the Model failed to serialize and will be an empty string if serialization was successful. An attribute called “errors” will contain a list of JSON objects for each invalid issue. A boolean attribute called “valid” will note whether the Model is valid or not.

Default:

True

-f, --output-file <output_file>

Optional file to output the full report of the validation. By default it will be printed out to stdout.

Arguments

MODEL_FILE

Required argument

rooms-solid

Validate whether all Room volumes in a model are solid.

The returned result can include a list of all naked and non-manifold edges preventing closed room volumes when –json is used. This is helpful for visually identifying issues in geometry that are preventing the room volume from validating as closed.

Args:
model_file: Full path to a Honeybee Model file.
honeybee validate rooms-solid [OPTIONS] MODEL_FILE

Options

--plain-text, -j, --json

Flag to note whether the output validation report should be formatted as a JSON object instead of plain text. If set to JSON, the output object will contain several attributes. An attribute called “fatal_error” is a text string containing an exception if the Model failed to serialize and will be an empty string if serialization was successful. An attribute called “errors” will contain a list of JSON objects for each invalid issue. A boolean attribute called “valid” will note whether the Model is valid or not.

Default:

True

-f, --output-file <output_file>

Optional file to output the full report of the validation. By default it will be printed out to stdout.

Arguments

MODEL_FILE

Required argument