Update 2020-02-03

[theo-armour]

Honeybee Viewer 3D 2020-02-03

• F: Add link to Builder
• R: Turn off gaming mode
• F: Add gfb-github-file-builder-2020-02-03.js
  • Honeybee JSON Schema sample files from ladybug-tools/spider on GitHub.

honeybee schema builder 2020-02-03

• F: Add multiple rooms with six faces each
  • Rooms placed randomly in 3D space

To Do / Wish List

• Add all the meta data
• Add all types of shades
• Add all types of openings
• Add any number of stories
• Add any number of plan types

[mostaphaRoudsari]

@theo-armour, so much is going on here in a very positive way.

Your wish list is what I wanted to wish for so I don't comment there.

For the mouse over is it possible to see the face type or properties.energy.construction instead of UUID and ID. They are not really as useful to the end user.

Am I right that the schema builder converts a THREE.js mesh to honeybee schema? That's a very nice proof of concept on how the schema can make it easy for other tools to access Pollination.

[theo-armour]

For the mouse over is it possible to see the face type or properties.energy.construction instead of UUID and ID. They are not really as useful to the end user.

I have not figured out a good way of linking the 3D face back to its parent JSON data. In gbXML, every element has a unique ID, so it's easy. Here there is only the Name property - which may or may not be unique and will need more checking.

Certainly today, I could just copy all the room and whatever data from the Schema JSON to the Three.js JSON at load time, but it will be nice to make the link between Schema and Scene interactive at run time.

In any case, this is part of overall thinking behind the Schema - and I still have much to learn about your plan of attack. This is already being discussed in Honeybee Schema repo, we should continue there.

Am I right that the schema builder converts a THREE.js mesh to honeybee schema? That's a very nice proof of concept on how the schema can make it easy for other tools to access Pollination.

Bingo!

Any geometry that can be built in Three.js will be translatable to Pollination data. Shades that move, roofs to stadia that open and close, mobile homes that morph shape, projects that get built over a period of years: we can handle these! Three.js is used to create games, fold proteins, do ray-tracing and more. As they used to say at Autodesk: "the only limit is your imagination!"

[chriswmackey]

@theo-armour ,

This is looking spectacular!

To quickly respond, the 'name' is always unique. Otherwise it's not a valid Honeybee JSON and it's not a JSON that can yield valid simulations. Maybe we should have just called it 'id' instead of 'name' and simply called the 'display_name' 'name'. It's just that all of the simulation engines refer to what you're thinking of is an id as a name and maybe we were wrong to continue this precedent. In any case, you can use the name to link between the schema and the scene and there shouldn't be any issues with valid JSONs.

[michaldengusiak]

Could we align colours so we have consistency among tools? and everyone is familiar with the same colour for types :) among all tools
ladybug-tools/spider#42 (comment)

SurfaceType | Color Hex
InteriorWall #008000
ExteriorWall #FFB400
Roof #800000
InteriorFloor #80FFFF
ExposedFloor #40B4FF
Shade #FFCE9D
UndergroundWall #A55200
UndergroundSlab #804000
Ceiling #FF8080
Air #FFFF00
UndergroundCeiling #408080
RaisedFloor #4B417D
SlabOnGrade #804000
FreestandingColumn #808080
EmbeddedColumn #80806E

[mostaphaRoudsari]

If it is similar to the OpenStudio color-set then I very much like the idea. Not that I "love" those colors but I DO LOVE consistency. =D

[chriswmackey]

Color consistency would be wonderful. From what I can tell, those colors are the same as what OpenStudio uses, though I'm used to seeing the ceiling color for interior floors (I guess Openstudio only renders one of the two given that these geometries are the same).

I also see that there's no color given for windows but this is usually light blue with some transparency.

[theo-armour]

Stephen Roth is advising Spider on the gbXML stuff. He wants more architects to use gbXML. He is asking for prettier rendering. Therefore I am currently playing with colors, fog and more in the various viewers.

Upcoming releases will also include textures. These could display heatmaps, but the could also be used to show bricks and slates etc or construction stages or exposure direction. In any case the color and texture of a surface should be thought of as a fixed thing but should be considered as a highly valuable parameter useful in displaying a variety of construction parameters such a r values, fire resistance, thickness, reflectance and whether openings and shades are open or shut