You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Access online and local gbXML files via URL, file ope dialog box and drag&drop
Run an extensive set of checks - with most checks also providing automated fixes
Save fixed models as .XML or .ZIP files
The following are the checks and fixes currently implemented:
Inspect files in real-time 3D
Check for valid text and numbers
Check project offset distance from origin
Check for openings with more than four vertices
Fix missing required gbXML attributes
Fix surfaces with invalid surface type name
Fix surfaces with invalid ExposedToSun
Fix surfaces with duplicate planar coordinates
Fix surfaces with an extra adjacent space
Fix surfaces with duplicate adjacent spaces
Fix air surfaces with single adjacent space
Fix Surfaces with CAD object ID missing
Using the Fixer should be much easier than doing searching for and replacing text in a gbXML file and should be faster than using the Spider Viewers.
Notes
The current release establishes a system of modules that should be fairly easy to modify and add to.
A number of features are embedded in each module to help humans with testing. Future releases - once a module is well-tested - could do away with the human-verification aspects and simply fix the issues with a single click.
In the coming week, there will be testing on all the available sample files. A few additional modules may also be created. Work will continue on making all modules have the same user interface. And bugs will be fixed.
In the following week, announcements will be made on the Ladybug Tools Forum and other suitable venues along with requests for test cases.
The text was updated successfully, but these errors were encountered:
That semantic versioning is a @AntoineDao's effect! :D
I have one quick question:
How Inspect files in real-time 3D is different from 3D viewer itself? Do we consider this as visual check? @theo-armour are you thinking that the editor and fixer will be part of the same application at some point?
Ultimately the Fixer should be a straight 'ascii' app with no visualization whatsoever. In theory there will just be one button that says "Fix it!". But at this early stage, some guidance for humans is needed for for testing.
There will be more about this in the announcements. The enemy is peeps clicking six time to fix an error and there sixty errors to fix.
This week turned out to be a big code clean up. Most of the modules now have very similar code and functionality. Once you learn one module it should be easy to use - and to edit the code - of any other module.
Most modules allow you to fix and view the proposed changes for one surface at a time. This is to help you with testing and verifying the results. The the entire text of the edited surface is viewable in a text area - so you can check what happens.
But please note: the goal is that you never have to do this in the future. If we get things right, then the 'Fix all' button should do exactly what they say.
theo-armour
changed the title
Spider gbXML Fixer 'Atrax' R0.4.7
Spider gbXML Fixer 'Atrax' R0.4.7 >> 2019-05-18: R0.4.13.1
May 18, 2019
@ladybug-tools/spiders
Spider gbXML Fixer 'Atrax' R0.4.7
Note new semantic versioning-compatible numbering
Spider gbXML Fixer enables you to:
The following are the checks and fixes currently implemented:
Using the Fixer should be much easier than doing searching for and replacing text in a gbXML file and should be faster than using the Spider Viewers.
Notes
The current release establishes a system of modules that should be fairly easy to modify and add to.
A number of features are embedded in each module to help humans with testing. Future releases - once a module is well-tested - could do away with the human-verification aspects and simply fix the issues with a single click.
In the coming week, there will be testing on all the available sample files. A few additional modules may also be created. Work will continue on making all modules have the same user interface. And bugs will be fixed.
In the following week, announcements will be made on the Ladybug Tools Forum and other suitable venues along with requests for test cases.
The text was updated successfully, but these errors were encountered: