Commands for comparing Honeybee objects.
honeybee compare [OPTIONS] COMMAND [ARGS]...
Get a report outlining the differences between this model and another.
The resulting report will only note top-level objects that are different between this model and the other. If an object has not changed at all, then it will not show up in the report.
Changes to geometry are reported separately from changes in metadata (aka. extension properties) for each of the top level objects.
If the Model units or tolerance are different between the two models, then the units and tolerance of this model will take precedence and the other_model will be converted to these units and tolerance for geometry comparison.
honeybee compare models [OPTIONS] BASE_MODEL_FILE OTHER_MODEL_FILE
- --include-deleted, -d, --ignore-deleted¶
Flag to note whether objects that appear in the base model but not in the other model should be reported. It is useful to ignore-deleted when the other model represents only a subset of the current model.
- --include-added, -a, --ignore-added¶
Flag to note whether whether objects that appear in the other model but not in the current model should be reported.
- --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.
- -f, --output-file <output_file>¶
Optional file to output the full report of differences between models. By default it will be printed out to stdout