Integrating ability to have multiple windows into Qline

[antonszilasi]

@theo-armour Unfortunately I am struggling to get the the multiple window functionality working with the qline code,

I managed to do it easily with r12 please see here

The closest I have got is the code here Which you can see here: https://antonszilasi.github.io/spiderAnton/speed/speed-page.html As you can see although I do have multiple windows they all appear onto of each other.

How can I space these windows out over their parent surface, can you please provide an example.

[theo-armour]

@antonszilasi @bwelle

I can't begin to count the number of silly things I have created in this project. This started from the get-go when I spent a day or so creating a NURBS chart cookbook example when what you needed was a scatter plot example. So let's help me not make a mistake this time.

I understand your struggles with the various gbXML building generators. I have them too. As far as I know there are zero examples of open source code available for this type of thing. We start from scratch. We make mistakes. We fix or we end game / go back to start.

So in order to move fast and effectively, let's help me build it right.

What are the inputs?

• Everything in feet/inches/%?
• HTML input type=range or input type = number?
  • Decision required for each numerical input
  • If input type=number indicate if you want error checking for entering letter or negative numbers etc
• A window to wall ratio of percent with 1% min and 99%?
  • If you want 0% and 100% then these are likely to be special cases where there is an external wall with no opening or a wall that is entirely opening. Such cases are likely to have impact on the exported gbXML let alone the 3D display
• The number of openings per elevation
  • Zero openings and large numbers of openings are likely to create special cases
• Overhang depth per opening with min max and step
• Fin depth per opening with min max and step
• Dimension and location inputs and constraints
  • Choose one of the following:
    • Length, height, center point, azimuth and tilt?
    • Three x,y,z points?
  • Vertical walls only?
  • Orthogonal/ tied to X-axis or Y-axis walls only?
• Any data particulars - relating perhaps to gbXML or whatever - that should be associated any of the openings

Once we've agree the above. And added the bits I forgot about, we can list and verify the outcomes we desire,

I would like to build a cookbook code sample as a response so a description of the problem we are trying to solve and how a solution might bring benefit would be totally cool.

[antonszilasi]

@theo-armour @bwelle

Actually after a fresh look at your qline code this morning - I managed to figure it out with the code: https://github.com/antonszilasi/spiderAnton/commit/4b83e57aeef46ac6b8db53307e441425b2e523c1

Please see: https://antonszilasi.github.io/spiderAnton/speed/speed-page.html

I realize now that you were interpolating to place the windows, I will now go through and add the overhangs and fins as well try and change the material propertys to make it more pretty.

At the moment what I think would be really helpful is if you could document your qline code as its pretty hard to follow in certain places.

Cheers,

[theo-armour]

@antonszilasi

At the moment what I think would be really helpful is if you could document your qline code as its pretty hard to follow in certain places.

Welcome to linear algebra.

I do my best to create scripts that require minimal documentation because the functions and variables are so exquisitely named and flow so logically from one to the next that if you know plain vanilla JavaScript, HTML and CSS and you are familiar with the basic principles of linear algebra and you can follow Mr.doob's examples you should be able to read my code. If you see any place in my code where names or flow could be improved I want to hear.

In any case, writing documentation for code that is already out of data does not appear to be could use of anybody's time.

In any case, bravo for finding a solution. Keep at it!

[bwelle]

Sounds good. I will put this all together tonight

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Theo Armour notifications@github.com Sent: Monday, November 13, 2017 1:02:37 PM To: ladybug-tools/spider Cc: Welle, Benjamin; Mention Subject: Re: [ladybug-tools/spider] Integrating ability to have multiple windows into Qline (#59)

@antonszilasihttps://github.com/antonszilasi

At the moment what I think would be really helpful is if you could document your qline code as its pretty hard to follow in certain places.

Welcome to linear algebra.

I do my best to create scripts that require minimal documentation because the functions and variables are so exquisitely named and flow so logically from one to the next that if you know plain vanilla JavaScript, HTML and CSS and you are familiar with the basic principles of linear algebra and you can follow Mr.doob's exampleshttps://threejs.org/examples/ you should be able to read my code. If you see any place in my code where names or flow could be improved I want to hear.

In any case, writing documentation for code that is already out of data does not appear to be could use of anybody's time.

In any case, bravo for finding a solution. Keep at it!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ladybug-tools/spider/issues/59#issuecomment-344056837, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbaYGkH8L3tYsGh54tR1DjGN7TIkYNerks5s2K5tgaJpZM4Qa-7h.

[theo-armour]

@antonszilasi @bwelle

wall with multiple openings overhangs fins

[bwelle]

@theo-armour @antonszilasi

Gentlemen. It feels far but we are close. Most of my confusion is due to why there is confusion. The gbXML export is actually very straight forward. I have done everything I can to be very specific in what needs to happen throughout a wide range of issues and on Confluence. Apparently, I was not as clear as I had hoped, and I know jumping back and forth between things is challenging. We actually were almost there with Build Well, then we took some steps back with q-line (you surprised us with that one Theo;)), then a few steps forward, then we did speed-specification, and we took some more steps back. Everything we want has happened at one point or another. We just need to synthesize and aggregate/merge. Let me try to take a step back and simply as much as possible for the final time, hopefully this will all make sense.

Please forgive me for any cookbook conventions I am violating...I'm just trying to communicate in a different way what I've tried and failed to do in every other possible way.

Please the cookbook SPEED Geometry Requirements and SPEED gbXML Requirements

[theo-armour]

And I thought this issues was about

Integrating ability to have multiple windows into Qline