Closed theo-armour closed 6 years ago
I wouldn't use OS to validate. It may may break for non-validation reasons.
Chien Si said he's not sure if it's how we are using it or if there's an issue with the validator.
Yes, current validator is very confusing as only validates few test cases files. I would highly recommend this one created by Karlsruhe Institute of Technology.
https://www.iai.kit.edu/english/1302.php
Go to query and can see warnings/errors and save as xml file. This could be aslo some inspiration for warning/error finding
Isn't this more of a viewer rather than validator? I.e it might be very forgiving in way we don't want it to be? Maybe not, just thinking out loud.
Hi, it is viewer but also list all issues and errors and warning with gbXML structure. This could be good to see where file have fundamental problems.
Got it, thanks.
The validator that gbxml wrote is not intended to consume any gbxml file. That is what the industry wants, but gbxml has yet to provide. All the validator does is just allow you to draw a test case in your tool (spider/build well), export it, and upload it to the validator.
If you want something that is more generic, then the options are to import it into a desktop viewer/validator as some others suggested. Ultimately, you'll want to put it through OS.
I still say we want to validate visually or otherwise prior to OS. If it looks good, then we ping OS.
Interestingly enough, I took the gbXML file that was one of the only test cases from Chien Si (clean files) that worked in OS, and I just uploaded and tested with whole building test and it failed miserably, couldn't even generate error log. Wonder what the other test numbers are. Am I using the right xsd?
I don't think you guys are fully grasping what that validator is doing.
On Wed, Oct 4, 2017 at 4:43 PM, bwelle notifications@github.com wrote:
Interestingly enough, I took the gbXML file http://url that was one of the only test cases from Chien Si (clean files) that worked in OS, and I just uploaded and tested with whole building test and it failed miserably, couldn't even generate error log. Wonder what the other test numbers are. Am I using the right xsd?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ladybug-tools/spider/issues/35#issuecomment-334283465, or mute the thread https://github.com/notifications/unsubscribe-auth/ADJ-2ZIFkye7lAK1vT0txPB_Kd7b5IGhks5so-3qgaJpZM4PuImD .
Hmm, I assumed it checks for minimum required objects, correct surface definitions, adjacencies, coordinate ordering, etc. No?
No. Wrong assumption.
On Wed, Oct 4, 2017 at 4:47 PM, bwelle notifications@github.com wrote:
Hmm, I assumed it checks for minimum required objects, correct surface definitions, adjacencies, coordinate ordering, etc. No?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ladybug-tools/spider/issues/35#issuecomment-334284484, or mute the thread https://github.com/notifications/unsubscribe-auth/ADJ-2Xq_JfeJduXYDdBlyg-s3Xt2dWSWks5so-7ggaJpZM4PuImD .
Theo, I spoke with Chien Si, I get it now. The validator is looking for specific test cases, geometry, for vendor certification. It can't just just take any gbXML and generically check it. So it's useless to us. We should use the tool suggested above to inspect, or just pop it into the gbXML JSON viewer to check (I say we start with the former). If all looks good, give it to Anton and he will ping the OS API and see what happens. We go from there.
There is few fundamental geometry checks that I would be good to implement. Currently many people use Revit to generate gbXML and code they use is not perfect. So would be good to have:
Hi Theo,
I can help with the validation. I did this stuff for thermal models for a long time (remember that document I sent you?!) So you can generate gbXML files, and I can visually inspect, and if looks good pass to Anton to ping the API with. Does this work for you? I'm assuming you want your own way to validate without a downloaded viewer.:) Maybe put into the gbXML JSON viewer or regular viewer I see on Spider?
Sounds good.
The dev version of BW gbxml exporter is now handling Box and L Shape geometry. Now working adding the attributes. Should have something to inspect soon. I am going to a friend's lecture on robotics in an hour. Don't know when I will be back.
On Wed, Oct 4, 2017 at 2:43 PM, bwelle notifications@github.com wrote:
Hi Theo,
I can help with the validation. I did this stuff for thermal models for a long time (remember that document I sent you?!) So you can generate gbXML files, and I can visually inspect, and if looks good pass to Anton to ping the API with. Does this work for you? I'm assuming you want your own way to validate without a downloaded viewer.:) Maybe put into the gbXML JSON viewer or regular viewer I see on Spider?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ladybug-tools/spider/issues/35#issuecomment-334298344, or mute the thread https://github.com/notifications/unsubscribe-auth/AAhbKljXni6Yq8_Rx7SMzehI-gUoEXefks5so_vpgaJpZM4PuImD .
@mdengusiak
Thanks for link to Karlsruhe Institute of Technology validator. I will download and try it out.
@ladybug-tools/build-well
I have downloaded and installed Open Studio. I have started experimenting with it. I have been able to correct two issues it reported which then enabled me to progress further through the import process.
Currently Open Studio is reporting messages like this: Surface 'bw21' is not assigned to a space
Therefore it appears Open Studio is able to get all the way through the files Build Well > gbXML export is creating. It appears that once the 'Space' items info are added, the import could be good.
Fingers crossed, this gets dome in the next day or so.
@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?