ladybug-tools / spider

:spider_web: 3D interactive analysis in your browser mostly written around the Three.js JavaScript library

You are now in a GitHub source code view - click this link to view Read Me file as a web page

Spider Read Me

<iframe class="iframeReadMe" src="https://www.ladybug.tools/spider/plugins/iframe-carousel-r1.html" width="100%" height="480px" ></iframe>

All of the above are embedded interactive scripts available here

Ladybug Tools / Spider: Latest Issues

Ladybug Tools / Spider gbXML Tools: Latest Issues

Ladybug Tools / Spider gbXML Fixer: Latest Issues

Examples of interest in this repo

• gbXML Viewer R12
• gbXML Viewer Dev R13
• gbXML Viewer Dev R14
• Analemma 3D
• Burning mAnalemma 2017
• Spider gbXML Viewer Previous Releases

---

NREL's OpenStudio Includes Spider gbXML Viewer

Spider gbXML Viewer is embedded in latest release of OpenStudio. See the Ladybug Tools forum for details.

The code for the OpenStudio edition is maintained in a new repository: Spider gbXML Tools. This code is simpler, faster and better than the current releases.

So have a look at Spider gbXML Viewer Basic and all the modules in the Cookbook. These scripts will be the basis for future release of the Viewer.

Green Building XML Webinar

gbXML.org held a webinar for the 'Aragog' gbXML Viewer on Tuesday, May 8 2018.

• Moderator: Stephen Roth
• Presenters Chris Mackay and Michal Dengusiak

Video: https://www.youtube.com/watch?v=qHFEhD2SsDA

Invitation: https://conta.cc/2H7ex7f

Webinar Files 2018-05-08

---

YouTube Video: gbXML Viewer ~ User Guide

• Michal's and Michalina's must watch video on Spider gbXML Viewer
  • Tania Becker: 'Fascinating video. It's well explained and easy to understand even for a lazy person. It sparkles!'

---

Concept

Issue / The problem to be solved

The purpose of the Spider web presence is still a work-in-progress.

The main issue is that much of the currently available software for carrying out building visualization and analysis is expensive, hardwired and not easily accessible.

Solutions to these issues might include:

Provide free, simple, easy-to-access tools to enable an analysis of building outcomes earlier in the design process - or even as a stimulator of the design process

Offer easy-to-read code written so that designers and engineers may monitor, verify and enhance the efforts - and, yes, full-stack developers are welcome too.

Enable just-in-time custom solutions. Every building is both unique and standards-adherent. The visualization and analysis tools should be the same.

Mission

Things we seem to be doing include:

• Displaying gbXML files in 3D
  • See gbXML Viewer
  • See gbXML User Guide
• Create new gbXML files and view these in 3D
  • See Build Well
• Displaying EPW files in 3D
• Displaying solar calculations in 3D
  • See Analemma 3D
  • See Ladybug Tools/Ladybug Web/
• Displaying large complex data sets in 3D
  • See NURBS Chart
  • See Scatter Well
• Displaying fun hot stuff in 3D
  • See Burning mAnalemma 2017

Vision

Life here on Earth is quite amazing and enjoyable. We'd like to help make Earth even cooler.

Links of Interest

See also these two links below for previous-related efforts.

• https://ibpsa2017.github.io/
• http://www.ladybug.tools/ladybug-web/

Thoughts we like:

• https://readmetips.github.io/
• https://opensource.guide/
• https://www.w3schools.com/howto/

Technology that helps beginners build more technology

• https://glitch.com/
• https://bl.ocks.org/
• https://threejs.org/
• https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API

---

spider's Issues

2017-09-21~ Build Well R4

@ladybug-tools/spiders

Full Screen: Build Well R4

Source code: https://github.com/ladybug-tools/spider/tree/master/sandbox/build-well

Change Log

• Supports basic Box Shape and L Shape
• Open openings
• Perimeter depth walls
• Exportable text building data
• Each module works/tests as standalone and also as a component in a container

Burning mAnalemma R2

@ladybug-tools/core

Animated GIF of Burning mAnalemma R2

Burning mAnalemma R2

After a slow start yesterday, more slow progress. At least screen capture was added. We now have something to show that we now have something.

A lot more good stuff coming up. I hope to have updates / new releases every day of Burning Man.

What slowed things down today was the back end - but good progress was made.

The mission is something like this:

• Single index.html
  • Handles opening and displaying any and all files in sub-folders and whereever
• Single main menu
  • Written in Markdown
• Multiple sub folders
  • All files accessible from main menu
• Multiple scripts
  • Content may be Markdown of HTML in an iframe
  • Menus can be markdown or HTML in an iframe
  • Allows menus to behave like dialog boxes
• Multiple sub menus
  • Scripts loaded at run time
• Multiple Read Me
  • Every folder can have its own read me
• All hosted as static files on GitHub/Bl.ocks.org/Glitch or wherever

gbxml Export plan of attack

@theo-armour

I have had a close look at the json file that is exported when the 'the building' object is sent to ToJSON, please find it attached here (not in JSON form I could only attached it as a text file).

I am quite confused about the format that MR doob has used for two reasons:

1. Under the geometries heading: I see that each geometry has a list of shapes which have curves which then have points which makes sense - but why do these points have no z coordinates? It seems that there is not a single z coordinate in the whole file.

2. Each geometry under the geometries heading can be related to an object under the Object heading using a uuid. Each object has a Matrix, which as I understand it is not useful for what we are trying to achieve here, correct?

In light of the above, it seems that the best approach would be to take the name: which you have applied to each mesh and work some code to convert this into gbxml form. Do you think that this would be the best approach?

building.txt

Update 2017-10-16 ~ Build Well R11 ~ better geometry handling

@ladybug-tools/spiders

Updates to Site Settings menu

Full Screen: Build Well R11

Another big update. Last time it was the menus, this time it was the geometry handling.

The whole package now has quite a few loose ends. The next few pint releases should begin to clean things up a bit

Coming up next is

• Bring the L Shape up to the level of the Box Shape
• Work on Zones and Spaces menus
• Work on Anton's WWR menu
• Separate ft/in and metric menus. Also multiple languages maybe
• gbXML export needs rotation and overhangs

Change Log

• R11
• New geometry handling process
• 'The Building' is always in shape
• Kicks off as a Box Shape from get go
  • Created as a JavaScript object that exists throughout session
  • Geometry can come and go, but defaults and most variables persist
  • Should make it easy to switch between shapes
• Site Settings
  • Now includes Location and Units details
  • Units not yet wired up to other menu

To do list items mostly dealt with

• 2017-10-14 ~ Open with Box Shape already in place
• 2017-09-22 ~ Add lat & Lon

Logo for spider

@ladybug-tools/ladybug-web-admin, do we need a logo for this new insect, spider? :)

Update ~ 2017-09-12 ~ gbXML Viewer 'Harriman'

@ladybug-tools/core

gbXML viewer harriman

Mission

• View gbXML files in 3D in your browser
• Full zoom, pan and rotate
• Run on computer, tablet and phone
• Adjust a wide variety of viewing parameters
• View the full gamut of data typically available in a gbXML file
• Open files via URL or open file dialog
• All free and open source hosted on GitHub

Vision

• Helping students, clients and non-AEC peeps gain access BIM data easily, quickly and freely

2017-08-29 ~ Burning mAnalemma R4

@ladybug-tools/core

Are you climbing Mountelamma Everest? Bring the Burning Man Temple with you.

Burning mAnalemma R4

• Menu structure simplified. Still needs more work though
• Adds the Temple as a parametric component
  • Adjust overall Temple width and depth, individual timbers width and depth
• Add more destinations

Build Well Road Map

@ladybug-tools/spiders

This issue is for ongoing discussion regarding regarding the purpose, usage and development of Build Well.

As of this writing Build Well is being developed to help a particular firm develop its own particular use case. This is intentional and its mission. It would also be nice to envisage and build for other usages.

If nothing else, it is likely that some of this code will be part of a 'Room Well' or 'Space Well' project with Mostapha's guidance.

This issue is not a good place for discussion regarding issues with current releases. These should be discussed in the various issues under the 'Updates' label.

Any and all thoughts, comments and suggestions appreciated and welcomed.

Build Well U-Shape Updates

U-Shape specific issues may be discussed here.

Update 2017-10-11 ~ Build Well R9.1

@ladybug-tools/spiders

Full Screen: Build Well R9.1

I was about to give up on getting walls with openings into Open Stdio, but finally things began to fall into place. There's still overhangs and fins to be added which should not be difficult. And another horror still to be completed is building orientation.

The main thing is that the gbXML file is starting to look clean. And we can start to explore what further data can be added by algorithm.

Change Log

• Build Well R9.1
• Exports gbXML files with exterior wall surfaces with openings that render properly in Open Studio
• Box Shape now equal of L Shape
• Orientation fixed
• Code clean-up

Update ~ 2017-09-28 ~ Build Well R7

@ladybug-tools/spiders

Full Screen: Build Well R7

Change Log

The menu system is more robust, enables the display of Markdown format files and enables switching menu items without losing data.

It will also facilitate the development and display of the JSON and gbXML export capabilities

• R7
• Menu and file handling rebuilt
  [x] 2017-09-23 ~ Better handling of data when switching tabs after a shape has been created
  [x] 2017-09-21 ~ See if perimeter depth diagonals actually add any pertinent information
  • Rule of thumb: Show what you will export and no more.
  • Currently the external wall and perimeter depth walls provide sufficient data for downstream apps.
    [x] 2017-09-21 ~ Finish add data reporting parameters, eg openings, adjacent buildings
• 2017-09-22 ~ Consider more suitable name for this menu item
• 2017-09-22 ~ Add ground that can receive shadow
• Add quite a bit of text to read me

gbXML color palettes /schemes for surface types

according the gbXML-Schema, gbXML has the following types of surfaces:

• InteriorWall
• ExteriorWall
• Roof
• InteriorFloor
• ExposedFloor
• Shade
• UndergroundWall
• UndergroundSlab
• Ceiling
• Air
• UndergroundCeiling
• RaisedFloor
• SlabOnGrade
• FreestandingColumn
• EmbeddedColumn

Future releases of gbXML Viewer and Build Well will enable the ability to display each of these surface types with its own colors, textures or shaders. Right from the beginning it would be nice to have a variety of color palettes or schemes available.

I note that @mdengusiak kindly posted a list of colors for many but not all here: #16

1. Does anybody have or know the location of any standard (or non-standard) gbXML color schemes that covers all surface types?
2. Are there any surface types not in the Schema that we should be covering?

2017-09-18 ~ Build Well R1

@ladybug-tools/spiders

Full Screen: Build Well

Source code: https://github.com/ladybug-tools/spider

2017-09-18 Current status

Buildings Menu

• Three buildings created by default
  • Add and delete buildings: future release
• Save file
  • Saves buildings as a single 3D object
  • All data stored in the 3D models
  • File format is standard Three.js JSON
  • Seems to be working just fine
  • Many more options will become available
• Open file
  • Works barely OK
  • Building data fields are updated but edits do yet update geometry
  • L Shape models not being loaded. Try using JSON loader instead of Object loader

Site Context Menu

• When played with after a fresh reload, mostly works just fine
• Needs error-checking and more user entry safeguards
• As mentioned above, editing is broken when opening a file

Geometry Menu

• Mostly unfinished, only a few items work
  • Changing floor height updates some of the other fields
  • Footprint shape draws a partially parameterized L Shape - very badly
• A work in progress

Change Log 2017-09-17

• First commit

NURBS Chart Random Numbers

@ladybug-tools/core

NURBS Chart Random Numbers

Concept

Generating smooth meshes from a limited number of controls points is tricky.

NURBS offer a good solution

Three.js has a NURBS plugin

This is a preliminary example just to get going. It would be great to have some sample data to graph

Mission

• Simple ways of generating complex curves
• Useful for charts
• Useful for 3D modeling

Vision

• One day: create a routine that creates a smooth transition between two NURBS surfaces

2017-09-22 ~ Build Well R5

@ladybug-tools/spiders

Full screen: Build Well R5

Source code: https://github.com/ladybug-tools/spider/tree/master/sandbox//build-well/

Questions

@bwelle @antonszilasi

• Would you define or explain 'overhang' as used in this context? Is it something to do with the distance of the plane of the window panes to the plane of the facades? Link to authoritative illustrated reference is always cool.
• Should 'The Building' offset and orientation be set in its shape menus or in the Adjacent Buildings menu?
• Should 'The Building' have an offset? Or should it always have its origin at lower left corner at 0,0,0?
• Should orientation of 'The Building' occur at its center point or its lower left corner?
• Currently Building Area and Floor Area are read only and are updated whenever length, width or number of floors are updated. Is this satisfactory?
• How would you improve the vertical order of items the Box Shape menu ?

Change Log

• build-well.html
  • Iframe is more full screen
  • Cut out geometry and L Shape for time being: let's get Box Shape right first
    • Aspects of the geometry menu and shape menu are combined into one, Even though many of the parameters in the geometry menus are the same for all shapes, the code behind each of the parameters may be quite different. All shapes have areas, but the code for calculating the area of an L Shape is different from calculating the area of a Q Shape. In order to keep the code simple, it makes sense to duplicate the parameters for each shape.
• mnu-site-context.html
  • Orientation is now input type number instead of type range
  • Added updateGridSize
    [x] 2017-09-20 ~ User can update size of grid
• mnu-box-shape.html
  • All aspects of the relevant geometry may be set from this menu
  • All menu parameters interact
    [x] 2017-09-21 ~ Floor area to update according to shape parameters
  • Wall Window Ratio now operates as desired, updates model in real-time
  • Save building data to csv files using Ben's format
• Numerous CSS fixes

Update ~ 2017-09-28 ~ Build Well R6.1

@ladybug-tools/spiders

Build Well 6.1

Testing on Chrome and FF on Win 10, Chromebook and Android phone.

L Shape works sort of - but the area / length floor calculator is nor yet operable.

Change Log

• build-well.html
  • Add link to read me on menu / looked into how best to add license
  • Add three.js stats indicator
• mnu-adjacent-buildings.html:
  *grid resize should work with negative offsets / tests ok in FF win
  • add building: the new building becomes selected automatically
  • mnu-adjacent-buildings.html: add self adjusting grid / rotation is clockwise / old-timey axis indicator: started
• build-well-threejs.html
  • delete large center axis indicator
  • rename three.js base file
  • build-well-threejs.html: add view buttons / update css / set max zoom distance
• mnu-shape-box.html: update calcs: area and length lead /
  • Overhangs depicted to scale, max distance set to 10
  • Add diagonal perimeter depth walls
• mnu-shape-ell-one.html
  • geometry looking good / updates well / lacks area update calculations
• Site context menu now settings menu and moved to bottom / update its css

Update 2017-08-39 ~ Burning mAnalemma R5

@ladybug-tools/core

_Animated GIF showing a pile of lumber transforming into a temple or a post-modern architectural deconstruction. You're choice.

Burning mAnalemma

• Dis-assemble and re-assemble
  • Piece of cake
    *wish list item: 2017-08-29 ~ Add step-by-step assembly process
• Custom animated GIF creator
  • Took longer to build

Build Well 3D Scatter Plot

Here is where we will discuss the 3D scatter plot. I assume we will have a separate Build issue for this.

Update ~ 2017-10-05 ~ gbXML Viwer mostapha.4

@ladybug-tools/build-well @mdengusiak

Full Screen: gbXML Viewer

This interim update is just to help with validating/verifying gbXML export files created by current release of Build Well

Change Log

• gbXML Viewer 'Mostapha'.4
• Very messy, broken release with one nice new feature
• Adds: heads-up display(HUD) that shows details/data of the surace currently under the corsor
• Displays more (not all) meta data in side menu

Update 2017-10-10 ~ gbXML Viewer R5

@ladybug-tools/spiders

Open Studio sample OSM file exported as gbXML and displayed in Ladybug-Tools/Spider/gbXML Viewer R5

Full Screen: gbXML Viewer R5

Core code is beginning to settle down. Need URL access to many more gbXML files for testing.

After a bit more code clean up and modularization, it might be time to start thinking about new features.

Change Log

• gbXML R5 ~ back to a regular numbering system
• Improve object higlighting
• Improve lighting and shading
• Improve camera & controls distance control
• Add opacity to buildings
• Add select materials
• And quite a few other fixes

Build Well Space/Zoning Integration

We will need this additional information for gbXML export.

Build Well Project Management

Deadlines

Ben has to show something cool to his peeps in November. So we should work backwards and see what need so to be done by when.

We want to get the visualization working for a Box, L shape for demo. Integration with GUI will take some time, but is critical path for ME work. Also deadlines for gbXML and 3D scatter plot. So let's try this for schedule...

This was the original schedule. I prioritized shape stuff since integration with MicroExcel was a concern...

Box-Shape- October 2nd
L-Shape- October 5th
Space/Zone Assignment- October 8th
gbXML-October 12th
3D Scatter Plot-October 18th

However, since you are focused on gbXML now, let's go with this...

gbXML-October 5-10th
Box-Shape- October 9th
L-Shape- October 11th
Space/Zone Assignment (viz, not gbXML)- October 13th
3D Scatter Plot-October 18th (want to discuss 2D view too, will send more info shortly)

Various task areas

Remaining tasks for Box other than bug fixes of current release (noted in release notes):

1. Put x,y,z axis on the ground plan, make it black and thicker so it's very clear to the user visually, and put letters x,y,z on them. 3D text.

2. Add new window inputs and logic to place window arrays. I sent you what I have, let me know if you need more.

3. If user goes back and changes total building area, length and width update based on ratios of building areas.

4. Add N,S,E,W letters to view. Calculate based on angles so updates as rotate building. Make letters 3D.

5. Create 2D view somewhere that updates with 3D. Orthographic view like you said. Show equations in 2D text along building sides. When first show box, show equations on each side (Length 1 for x side and Width 1= (Building Area)/Length 1 for y side). Once user starts entering new values for independent parameter (Length 1) or changing parameters that change dimensions such as # of Floors, Building Area, we want to start showing actual numerical value rather than equations. Maybe make “Show equations” and “show values” a toggle the user can choose from!

Cameras

We need to switch seamlessly between three types of cameras

• Perspective - usual god-mode 3D view
• Orthographic - 2D-like views
• Fly-through - to inspect projects from the inside

BW-I don't think fly through is critical path now. They can zoom in if they want.

This will take a day or two to prepare some demos and see if acceptable

Text

Text is 3D has a number of interesting qualities

• Normal 2D text is difficult to read when you look from behind. And looking from behind is where you usually are.
• 3D text is neat but require hundreds of triangles to produce which can really slow things down - and you still end up looking from behind

Anyway, I will prepare some demos of possibilities

Debugging & Github

There's a lot to be done to get everybody up to speed on using GitHub effectively and being able to report errors effectively. I will be posting about both of these aspects.

gbXML

This looks like being the next big push: Getting Build Well to export its data in beautiful, clean gbXML.

Here is a personal issue: I do not download, install or compile ever. So would it be possible to build an online gbXML validator?

Something like

• http://jshint.com/
• http://jslint.com/
• https://jsonformatter.curiousconcept.com/

More immediately, I will need guidance in the naming and cataloging of every aspect of Build Well as it relates to gbXML. Perhaps we should start with a demo file and I try to get the exporter to match it.

Chien Si mentions 'We have prepared a very simple gbXML description that meets these minimum requirements.' but I've not yet discovered which file that is.

BW- Anton can help with this. You saw what Chien Si sent you. Not sure if that C# format is easily integrated. The gbXML functionality is less important now than getting the three.js stuff for the three shapes working.

Current Help Wanted

• Area/Length/Floor calculator for L shape, Ben can you post details as an issue?

BW-yes I will do this today.

• Currently, I don't happen to have any Apple products to test on. So hearing that things work on a Mac would be cool.
• The main thing to look at now is entering data in the various data input boxes and pushing to extremes or entering bad data. Fastest way is to use tab keys to jump between boxes and the to use up/down cursor keys to update values. if you can reproduce an issue - describe which box and what data was entered - please report.

BW-Will do.

3D Scatter Well and Google Docs Integration

@ladybug-tools/build-well

Scatter Well ~ Google Spreadsheet Data R1

Update 2017-10-22 ~ Build Well qLine ~ Saturday night coding

@ladybug-tools/spiders

Full Screen: Build Well qLine

Concept

This side project is an alternative to: http://rawgit.com/ladybug-tools/spider/master/build-well/r11/build-well.html

The code here is based on the idea of extruding a shape and making that shape follow a given path.

The code handles any shapes squares,, rectangles, stars, irregular polygons and so on. Whatever comes out of a pasta machine etc could be replicated here.

The path of extrusion - currently 2D only - may be made up of straights and curves. Pretty much whatever you can create as a line in SVG can be used as the path of the Qline.

Another thought is that there is no intention to create anything that looks 'realistic'. The idea here is to generate schematics quickly and easily. In order to speed the process a number of shapes can be displayed simultaneously.

One you are happy with a selection, adjacent buildings could be added and the ensemble exported as a gbXML file. When projects need to be shown to clients, then the files may b open and displayed using gbXML viewer.

And, as always, it's nice to have to see things in a fun, colorful game-like fashion.

Naming considerations

AutoCAD has a marvelous 2D drawing command titled 'polyline' - often called 'pline'

If one were to invent a new drawing command - designed to be what comes after the pline, then maybe it could be called a 'qline'. As in what comes after the letter P?

;-)

2017-10-21 ~ Theo

• First commit

More Robust Method to Define Parametric Geometry in Build Well

In the current version, there are limitations in the parametrics the user has at their disposal to define geometry. We have come up with a simple and robust way to give the user much more flexibility in defining geometry easily while minimizing inputs. This issue will be used to document this process to be added to Build Well.

new team + gbxml validation

@bwelle @antonszilasi @chiensiTB

you are now all members of a new team: @ladybug-tools/build-well

---

Am I correct in thinking that this validator is not that helpful at our current stage of development? Or do I just not understand how it works well enough?

Given the above, would it make sense for me to, biting the bullet, download and install Open Studio and so be able to verify Build Well gbXML export files in a more speedy fashion?

gbXML perimeter depth issue proposal

@ladybug-tools/build-well

In the current Build Well, if the length or width of a space is less than twice the perimeter depth then the interior wall is not created. For example, in the Box shape, reduce the length a lot to make a long very skinny building and watch all the interior walls disappear.

This was fine for getting started, but managing the gbXML zones and spaces if walls come and go, becomes much more complicated. And this probably makes the downstream calculations using zones and spaces even more complicated. This code can and should be written. but in this first generation of Build Well it may be better just to have a few simple rules.

I propose that:

All shapes have a minimum dimension of a little more than twice the minimum perimeter depth.

This means that all shapes all always have their normal set of zones and spaces. And there is always and interior zone - even if it's quite tiny.

If you choose a dimension of a space that is smaller than twice the current perimeter depth then the code asks you to reduce the current perimeter depth and try again.

Unless I hear a better suggestion, I will start to code something like this in an upcoming release.

Wish List - error list and highlights for gbXML

I really like your gbMXL viewer. Thanks a lot.
I would like to add to your road map/ wish list one more item. For me oen that could help and transform way how we use gbXML.

Currently working on many international project 90% of my projects are done in BIM in fact Revit.
Current revit gbXML generation engine is "not perfect", will be polite here even if I build perfectly model from scratch myself using very unrealistic simple rules. Would be amazing if we could allow your viewer to list also area where errors are. In step one just as simple geometry check.

Here is example. Simple building and there are two spaces that internal wall do not have two spaces assign to construction.

Maybe we could scan model and check all surfaces that are not external and highlight them in viewer if do not have two spaces assign etc...
Also zones with duplicate ID and surfaces with Duplicate ID.
We all could use this tool as model verification and then know exactly where to focus and what to fix.
We could even send this directly to Autodesk, Bentley and ArchiCAD in case there is issue with their gbXML export engine.

Looking forward to hear what do you think ,
Michal

Here we have Revit, TAS

here is your viewer..but something does not look right

Update 2017-09-30 ~ gbXML Viewer 'mostapha].1 ~ very holey release

@ladybug-tools/spiders

Full Screen: gbXML Viewer

Change Log

We have holes!

We display multiple files.

Coming next: Load files from disk. Colors, shade and shadows

• gbXML Viewer 'Mostapha'.1
• Displays surfaces with openings reasonably well.
• Speed is OK

Update 2017-10-16 ~ New Script: gbXML Guide

gbXML Guide

A growing list of what there is to be known regarding exporting and importing gbXML files

All data in Markdown files editable on GitHub

Build Well Project Management/To-Do List for Leadership Demo

@theo-armour @chiensiTB @antonszilasi

I have closed the previous Build Well PM issue and am creating a new update to date one. I will try to have this serve as a central location for all the various initiatives here on Git between Theo, Ben, Anton, Chien Si, etc. It will reference when appropriate other issues. Specific comments pertaining to a given issue should be made within the specific issue itself. If nothing more, this is a place for me to keep things organized in my head.:)

gbXML metric defaults

With the new menu system in Build Well and gbXML Reader, it is going to be much easier to build menus for different measurement standards and different languages.

In order to build the first set of demo menus, we need defaults, minimums and maximums for

• Perimeter depth
• Overhangs
• Floor height

@bwelle has supplied US defaults and these are what is currently available.

What should the metric defaults be?

And should we have separate demo menus for cm and mm standards?

Update ~ 2017-08-31 ~ Burning mAnalemma R6

@ladybug-tools/core

Burning mAnalemma goes to the Big Apple

Over at ibpsa2017,github.io Mostapha wrote:

What do you think about capturing some YouTube videos and create one of these from scratch. I know the code is open and easy to read but nothing replaces the power of seeing someone developing stuff and hearing their thoughts during the development.

Mostapha I hear you. I tell all people starting out - and experienced people as well - coders, artists, musicians whatever - that they should make YouTube videos. And I could probably get quite good at it. And that's the issue. And it reminds me of something that happened years ago.

For a number of years, whenever the then CEO of Autodesk, Carol Bartz, needed a demo of AutoCAD she called on me. And, frankly, she was right. I could make AutoCAD do amazing things. I could turn a then 2 1/2D system into a 3D system. I could play Pong on the screen menu. And I knew how to show it. Somehow - even with my one hand - I could keep things moving on three separate screens by myself. And I had an enthusiasm and liveliness second to none. Carol Bartz understood this. One of her comments I shall never forget: "We have to learn how to put Theo in a bottle."

So me making YouTube videos would certainly be putting me in a bottle and shipping me all over the world. And we should talk this over in detail in the near future.

In my brain though, I have a different obligation. I want to help people make their own bottles with their own personas as the contents. I want to mentor, provide cookbook code, describe specs, methods and ways of working that really engage people and help them become - as I was - excellent preacher/teacher/coaches.

So anyway, today's hack is about presentation.

• People want to explain their work clearly visually and aurally
• They want to explain it in English even when they themselves do not speak English that well
• They want to be able to explain their work in many languages besides English

A possible excellent tool is the Speech Synthesis engine in most modern browsers:

https://developer.mozilla.org/en-US/docs/Web/API/SpeechSynthesis

In response to your message, I brought this effort several days forward and today's hack is built up text to voice. It is nowhere near 'Theo in a bottle' level. Then again my first talk on computer graphics put everybody to sleep.

In the upcoming hacks I will try to embed voice - and sound - into the efforts. You ain't heard nothing yet!

Burning mAnalemma R6

Change Log

• Overheard on the Playa
  • Text to voice menu
  • Test button
  • Speak over twenty 'Overhread on the Playa' phrases
• About Map Overlay
  • Extra button on 'Overheard on the Playa'
  • Calls special helper script
  • Provides animated/visual/aural overview of the Map overlay functionality
  • Almost as good as Windows Paperclip

Update ~ 2017-09-29 ~ gbXML Viewer 'Michal'.2

@ladybug-tools/spiders

Full Screen: gbXML Viewer 'Michal'.2

Note: you may need to click the title in the left menu to get the script to to run the first time

Change Log

• gbXML Viewer 'Michal'.2
• Huge update! ;-)
• Handles all sorts of polyloop types - with good speed
• And I learned all about conjugating quaternions in the process ;-)

Cookbook first commit

@bwelle @antonszilasi

Can peeps take the crazy stuff we do here in Spider and embed it other normal peep's normal web pages? Good question.

Here's a first pass at an example:

http://www.ladybug.tools/spider/cookbook/multiple-3d-views/r1/multiple-3d-views.html

Will be ready for sharing tomorrow, but for now I'm off to the pub...

Update ~ 2017-09-13 ~ gbXML viewer 'carmel'

@ladybug-tools/core

gbXML viewer 'carmel'

The code is beginning to settle down.Is it time to start thinging about adding new features? Got any good idea?

see also: GreenBuildingXML/Sample_gbXML_Files#3

Change Log

• gbXML viewer carmel
• App titling automation
• Default menu box has random background gradient
• Select xml cleaned up
• Display gbJSON cleaned up
• Add draw edges
• Getting better: text file viewer

Update ~ 2017-09-04 ~ Burning mAnalemma R10

@ladybug-tools/core

Burning mAnalemma R10

Many updates since previous post. Getting near the end of this project. I treated it as a hackathon. And the results were hackathon like. Huge steps forward in a short amount of time.

I have half a dozen or more new tools to play with when visualizing building. These include - text to voice, making gifs, moving objects along paths, adding live sound, simplified parametrics, easy building disassembly/reassembly and more.

But what should the next project be?

Updates

2017-09-03

• R10
• Playa alive w/sound o"musex
• Howler.js + soma.fm
• News items for 31st, 1st, 2nd and 3rd
• 2017-07-31 ~ Add credits to Mapbox, Google, Mr.doob, GitHub and many others < started
• 2017-08-29 ~ Add aircraft flying about - with onboard camera < started
• 2017-08-31 ~ Add sounds and music

2017-09-02 ~ Theo

• R9
• Dancing in the Street - in your menu
  • 2017-08-29 ~ Add people dancing in the street

2017-09-01 ~ Theo

• R8
• Planes fkying much better
• Cockpit camera
• Aircraft changes type every fize seconds
• Can create animate GIFs with flying aircraft

2017-00-31

• R7
• Add start of credits page
• Add more tooltips
• Fixes to temple params, disassemble etc
• Make several plugins more standalone
• Add wireframe to Settings
• Add move temple vertical position
• Add BlackRock Airport Chick-en
• Create animated GIF - supports aircraft
• Default text with Daily news voice synth < part of the 'Theo in a bottle' effort

Update 2017-10-20 ~ Build Well R12 ~ spaces have individuated floors

@ladybug-tools/spiders

Full Screen dev release: Build Well R12

Save these links

• Build: http://www.ladybug.tools/spider/build-well << always the current (safe?) release
• Dev: <http://www.ladybug.tools/spider/build-well/dev > << the work-in-progress (may be broken) release
  fingers crossed one of them work for you

Note: gbXML export is a release of two behind the current geometry

Change Log

• mnu-template.html
  • Clicking on info icon takes you to source code
• build-well.html
  • Clicking on info icon takes you to source code
• mnu-box-shape.html
  • looking good: 2017-10-14 ~ add individuated floors and ceilings
  • id/zones numbers start from south side, run clockwise: 2017-10-14 ~ Revisit space id naming
• mnu-ell-shape-one.html
  • Clicking on info icon takes you to source code
  • correct issues with wall placements
  • looking good: 2017-10-14 ~ add individuated floors and ceilings
  • id/zones numbers start from south side, run clockwise: 2017-10-14 ~ Revisit space id naming
• mnu-hud.html
  • Mostly working as intended
  • working: 2017-10-14 ~ Highlight The Building when selected
• R12 started

2017-09-23 ~ Build Well R5.1 ~ 'When in Rome, do as the Romans do' Release

@ladybug-tools/spiders

Full screen: Build Well R5

Source code: https://github.com/ladybug-tools/spider/tree/master/sandbox//build-well/

Though this is numbered as a point release, it turns out there was a huge interesting change.

In the CAD/CAM world the Z axis is up. In computer science the Y axis is up. The defaults in Three.js follow computer science, which normally is fine because nobody cares about axes for the most part. But in CAD/CAM, XYZ is of the essence.

Up to now all the scripts in Spider have had Y as up. Until today. If Spider scripts are to help CAD users then, Spider should do as the CAD users do. So R5.1 is a rebuild of Build Well with Z as up.

Technically it's just about adding one line of code:

camera.up.set( 0, 0, 1 );

But mentally it is quite upsetting too. It turns your world on its side. ( I am not sure whether that is figuratively or literally. ;-)

Anyway a bunch of other nice things came in as well.

Change Log

• Add some prettifying to mnu-site-context.html.
• Z is the new up. X & Y now on the ground.
• L Shape is back but incomplete.
• Continued simplifying and standardizing across the scripts
• Shapes use center point of geometry as origin

---

@antonszilasi: are you receiving these messages?

Update 2017-10-25 ~ Build Well qLine R1.5 ~ You may start banging on it release

@ladybug-tools/spiders

Just for fun: a script to help you view the nine gbXML sample files created by Build Well qLine 1.5.

You may also use the script to open and view the XML source code for each file.

Full Screen: Build Well qLine

Full Screen: gbXML Sample File Viewer

There appears to be at least one issue with a surface near the roof - as reported by Open Studio. BTW Open Studio takes forever to load the file with 75 storeys - while our viewer loads it in a jiffy. Maybe this is because Open Studio is on a very old release of Three.js.

Anyway, I look forward to any observations. Please do differentiate between issues arising from incompletely specified objectives and issues likely due to errant code.

Barring any significant issues, the next activities will be to fold qLine code into the full Build Well scripts and to work on the parameters algorithms as well as looking at ways of assigning spaces and zones to particular attributes

Change Log

BW qline R1.5

• Update template with point release, and github icon variable
• build well: add go to top to menu bottom
• Settings/qline : fix building name issues
  • Add 'vertical separation' slider
• Make good progress on IDs and Adjacencies
• Create 9 sample gbXML files - one for each shape = with varying, floors, angles, spacing etc
• Create separate viewing applet - based on pre-release gbXML viewer R6

Mostly done or in progress

• 2017-10-25 ~ Fix Moire issues with openings
• Floor/Space/Zone IDs currently higgledy piggledy
• gbXML openings, floors and overhangs
• Fix section parameters so origin is at lower left
• Add IDs to HUD readout
• Fix site settings issues

Update 2017-10-14 ~ Build Well R10 ~ Many updates

@ladybug-tools/spiders

BW R10 showing new 2D report menu - while 3D model session is still active and visible in lower right corner of the window

Full Screen: Build Well R10

Read Me

Much of this upgrade was enabled by the prior effort here: Single Model Multiple Menus Read Me

This release fixes a lot of issues and enables a bunch of new features and will enable faster development. Having said that, it's still a puppy and it has not been tested much. Please wait unto 10.1 or 10.2 before hitting on it hard. Of course, if it crashes your system or you can't do something you think it should be doing then please do comment.

Ooops!! gbXML export is not working. Will fix ASAP.

In the mean time, just enjoy the new stuff. And do note that the code has been moved from the Sandbox folder up to the main Spider folder. Build Well is growing up!

Change Log

• Many updates to Read Me
• Add mnu-template as file and to menu
• Add groundHelper and toggle
• Added credits page - with first set of credits
  • Credits in menu moved to credits page
• Add the start of a 'real time report' page: menu + markdown + html
• Add start of a Settings Spaces menu - with spaces types etc
• Folder moved from sandbox folder to main Spider folder

Older items mostly dealt with

• 2017-10-10 ~ Menu interaction that does not revert scene and objects to defaults. Selecting various, Adjacent objects menu and Shapes menus, etc should maintain current set of object data
• 2017-09-29 ~ Some variables are hardwired to 'The object' string. Should be to whatever you want it to be ( & UUID ).
• 2017-09-28 ~ After going to 'read me' page, next page does not display properly - Click on title to reload the script
• 2017-09-29 ~ Add complete and current set of parameters to 'The object' object - to enable round trip with adj build menu
• 2017-10-02 ~ fix toggle edges
• 2017-10-02 ~ Ground & Helpers don't toggle after change in grid size
• 2017-10-02 ~ Add options to grid size / prevent spurious values
• Add links to credits page
• Enable viewing html & markdown without killing Three.js data

Update 2017-09-25 ~ gbXML Viewer 'Michal'

@ladybug-tools/spiders

gbXML Viewer 'Michal'

Source code: https://github.com/ladybug-tools/spider/tree/master/read-gbxml

Basic creation of 3D geometry still needs more work. Generating 3D faces is quite easy, but we want shapes with openings in them. This adds complexity. Anyway the next updates will be about basic geometry and - fingers crossed - adding openings.

Then we can get started on all of @mdengusiak's great wish list items - especially his color suggestions.

BTW, SAM Live - the new default drawing - was submitted by @mdengusiak . Thanks!

Change Log

• gbXML viewer Michal: mostly working
• Complete rebuild: smaller, faster smarter
• Simpler, more organized algorithms - probably faster
• Drawing a higher percentage of elements as Three.js
  • Some elements still flying off into space
  • Lines are drawn when shape has not been generated
• Z is up

Build Well L-Shape Updates

Let's use this issue for L-Shape specific issues.

Build Well gbXML Updates

Discussion forum for gbXML export functionality.

Build Well gbXML export

This new issue is meant to simply serve as the singular location to discuss dev efforts for the Build Well gbXML export for efficiency. Currently there are a range of comments etc. within a range of issues and it's difficult to keep things organized. After the next release of Theo's, we will use this issue to get the export to working form for the PW demo, focused on critical path items.

When there are general comments/suggetions/best practice, the discussion should be documented in the gbXML Guide for everyone's benefit, and referenced in this thread for convenience.

2017-08-27 ~ Burning mAnalemma R3 with hot new features

@ladybug-tools/core

Take the heat to Paris, Burning Man Temple 2017 in an animated GIF

www.ladybug.tools/spider/burning-manalemma-2017

Changes

• R3
• Add Geocoder
• Add Overlays
• Many CSS fixes
• Add zoom and pan terrain
• Add background gradient toggle
• Add settings menu

Many new features. Code getting a bit messy

Adds to spec started yesterday

• All scripts must be able to run standalone and within an iframe
  • Menus must be able to appear in both states
• Menus on the right
  • So as not to interfere with TooToo menus

2017-09-20 ~ Build Well R2

@ladybug-tools/spiders

Full Screen: Build Well R2

• Rebuilding in 'everything is a recipe' style.
• Currently three separate standalone scripts
  • Makes testing and coding and understanding what's going on a bit easier
  • Currently the data is not shared between the scripts. The liaison should happen in the next release
• Also coming soon will the internal walls, adjusting window sizes and the different shapes

Update 2017-09-29 ~ gbXML Viewer 'Mostapha' Release

@ladybug-tools/spiders

Full Screen: gbXML Viewer 'mostapha'

Change Log

Preliminary release. Only handles a single model.

Next release should have usual features plus: actual holes in the surfaces and not just black blobs. After that will come colors and shading

• gbXML Viewer 'Mostapha'
• Another big jump: now depicting Surfaces and Openings
• Code quite a bit smaller and tighter

Update ~ 2017-10-05 ~ Build Well 8.1

@ladybug-tools/build-well @mdengusiak

Full Screen latest release: Build Well

Please test: create a building. Save data to file. Open file with gbXML Viewer. Verify OK or issues.

Change Log

• mnu-gbxml-export.html
  • Beginning to export quite a bit of gbXML data
    [x] 2017-10-01 ~ Export all building geometries
    [x] 2017-09-30 ~ Floor area not being updated correctly

Build Well Box Shape updates

@bwelle

If you increase the total building area, how would you like the length and width of the building to update?

Am I correct in thinking the length stays the same and the width changes?