-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to change surface type now? #46
Comments
Sorry for slow reply to this issue. Somehow it does not seem to have made it to my mailbox. Or more likely I deleted the notice by mistake. There are several answers to your question. It depends on the type of error In Maevia v0.17.O2 in the Fixer menu > Fix air surfaces with single adjacent space. This is a basic check and needs more testing. In Maevia r15.3.5 there are the more sophisticated InteriorWall and InteriorFloor on exterior items. This code with 3D ray casting should reappear in upcoming releases and handle air surfaces as well. The overarching strategy is to leave behind humans searching for and fixing dozens of errors one error at a time to letting the code fix all the issues with a single click. For this we will need test cases and descriptions of the logic to follow. |
@theo-armour How can the Spider automatically recognize what is the void in the building: shaft or courtyard? |
See R15 https://www.ladybug.tools/spider-gbxml-tools/spider-gbxml-viewer/r15/spider-gbxml-viewer15.html Uses ray-casting. Any ray emanating from a wall that that passes through an even number of external surfaces must itself be external. Will be in v0.17 - and simplified - before too long |
@theo-armour |
@EK-CEL I got your point and this is correct... this is reason why we edit models and add missing and ask always Architect to put rooms for all spaces. This automation will be very complicated as to get it 100% correct gbXML we will require to add missing space/zone and close from top and bottom. How do we recognize what is shaft... I guess the most complicated here is geometrical modification but .... I wish we can fix all architect errors with one click ... :) |
@theo-armour @mdengusiak |
I agree in fact I am still using R12, as a manual workaround is still needed on most projects... let's see what we can do with @theo-armour in new version |
@EK-CEL @michaldengusiak @mostaphaRoudsari @chriswmackey @AntoineDao Evgeny and Michal: thank you for raising these issues.
I am glad you are happy with my 2017 and 2018 efforts. Please may I go away now? ;-)
Did you ever consider improving your GitHub skill levels? Since September 2019 I have been reporting Spider gbXML efforts here: https://github.com/GreenBuildingXML/GreenBuildingXML.github.io/issues See issues "closed' to verify. If you need a more detailed look at the Spider gbXML Viewer, here is a good link: https://github.com/ladybug-tools/spider-gbxml-tools/tree/master/spider-gbxml-viewer: If you would like to check out if I am being lazy, go here and look for the white boxes: https://github.com/theo-armour
Writing annoying software is the best. It means that there are users who are smart enough to understand they are being tortured. ;-) The interesting question is will the next revision be even more annoying or will the users stage a revolution? ;-) My personal feeling about 2019 was that I am 72 and my time on Spider projects was a waste of one of the few remaining years of my productive life. For example, here are ten Spider projects of interest that I worked on - not including the gbXML Viewer:
For a variety of good reasons none of these projects - and a number of others - went anywhere. In almost all the cases the reasons for lack of movement were the same: somebody said they wanted something but no test cases appeared, follow-up was almost non-existent and no spec was ever developed. There was no actual teamwork. My efforts on the Spider gbXML Viewer project were similar. Often I was sent a broken file and asked how to fix it because there was a due date approaching. Great architecture does not arise merely from being good about putting out fires. It would be nice if the 2020 objectives for the Spider project will be about enabling buildings are are more efficient, cost effective and pleasurable. And, fingers crossed, we build things that are less annoying. |
@theo-armour Thank you for the links, they are new for me. I will take a look what happens on other forks. I wish you to find a fulfilling objective for your activity. |
Thank you for your kind words. I know that both you and Michal have been my best supporters.
There is no requirement for you to learn GitHub. But what may be of interest is being able to spot activity and interesting things happening around Ladybug Tools. And that's what the links I sent are for.
Thank you. I have started drafting Spider objectives for 2020. First pass was here (at bottom): I should have a second draft up soon. |
Hello.
With the current Maevia version I don't see the ability to change the surface type on the right panel, i.e. from Air to Exterior Wall.
How can I do that?
Thank you.
The text was updated successfully, but these errors were encountered: