-
The Excel2IDS sample asks every external door to be True, and our own download tripped the tool
IDS Model Check now lists each cell where the Excel2IDS .exe would write a different IDS or stop. First finds: the template's sample and our own download.
-
We ran Excel2IDS on 321 workbooks: what reading its source missed
Running Excel2IDS's own tool confirmed the predicted differences and found two more: a version called None and _x000D_ in IDS files. It found a bug of ours too.
-
An IDS straight from a bSDD class: 185 classes, 42 dictionaries, every link resolves
IDS Model Check now writes an IDS from a bSDD class's property list, links included. Across 42 bSDD dictionaries, every link the tool wrote resolved.
-
Does your IDS link the bSDD entry it asks for? 7 of 53 public files don't
IDS Model Check now looks every facet uri up in the buildingSMART Data Dictionary. On 58 public IDS files, 7 link entries that don't exist or don't fit.
-
Excel2IDS workbooks, read in the browser and written back
The free IDS checker now reads a filled Excel2IDS template as one IDS per purpose and puts any IDS back into it. 309 of 309 public specs that fit survive.
-
Write an IDS in a spreadsheet, and open one in Excel
The free IDS checker now reads an .xlsx or CSV with one row per facet as IDS 1.0, and writes any IDS back as that table. 334 of 334 test files survive the trip.
-
IFC property sets have a home: occurrence-only and performance history sets in our IDS audit
Our IDS audit now reads buildingSMART's template types: 647 occurrence-set offers on type objects removed, and a false error on 86 performance sets fixed.
-
In an IDS pattern, an underscore is not a word character
XSD's \w leaves out the underscore and its \s leaves out the no-break space; IfcTester reads both the Python way. The IDS checker now asks which you meant.
-
A ^ in an IDS pattern matches nothing in IfcTester, and our checker said it matched
IDS patterns are XML Schema regexes, where ^ is a plain character. Four public IDS files and our own checker read them as JavaScript. Now fixed and checked.
-
Half the public IDS files that validators refuse can be repaired without a person
12 of 65 public IDS files break ids.xsd. A one-click repair brings 6 back to valid without changing what they ask, and found 48 facets our reader got wrong.
-
Room for sixteen: where our IFC checker's memory went after the parse
Checking a 219 MB IFC model against 68 IDS files needed an 896 MB heap. Exact-length lists and shared values bring it to 704 MB, same reports.
-
Our IFC checker's Map of entities cost as much as the entities
A heap snapshot showed a JavaScript Map holding 665,224 IFC entities cost as much as the entities. A plain array cut kept memory 21-30%.
-
buildingSMART's own IFC4 ifcXML examples made our checker count 4 walls as 24
We read buildingSMART's 41 IFC4 Annex E examples in both STEP and ifcXML. Seven ifcXML forms were misread; IDS verdicts now agree 129 of 129.
-
The biggest thing in our IFC checker's heap was the file itself
Reading STEP from bytes instead of one JavaScript string cut a 219 MB model's parse heap from 512 to 304 MB and opened a 670 MB file main refused.
-
A re-saved IFC model is not 8,975 new failures: GitLab Code Quality keyed on GlobalId
ids-model-check writes a GitLab Code Quality report. On real revisions it showed the 18 real changes, and nothing for a re-save renumbering 665,224 entities.
-
An IDS rule that can never apply, and how to tell before you have a model
IDS matches exact IFC classes, so a facet naming abstract IFCBUILDINGELEMENT selects nothing. The IDS audit now warns, and names the classes to use.
-
29 published IDS specifications name a list of classes; the editor now opens them
The free IDS editor now writes a specification for several IFC classes at once and offers only the property sets every one of them can carry.
-
143 of 210 classified elements in a Revit model have no code, and an IDS system check passes them
The free IDS editor now offers a model's attribute values and classification codes, and warns when objects carry a system with an empty code.
-
Check every IFC model against your IDS on each push: a free GitHub Action
One workflow step checks every IFC export in a repository against every IDS file, with annotations, a JUnit report and BCF files. Tried on four real models.
-
One public IDS specification failed 665,224 entities and took our CI runner down with it
Running public IDS files in CI found an out-of-memory crash and a hang on truncated files. Both are fixed, and the runner is six times faster.
-
Lenght, AkousticRating: the IDS editor now offers the standard name
17 rows in 7 public IDS files name a property one slip from the standard one. The IDS editor now says which name was meant and fixes it in one click.
-
External walls only: the IDS editor now narrows a specification by property, attribute or classification
The free IDS editor adds conditions to a specification's applicability and counts how many of an open model's objects each keeps, as the checker counts them.
-
When the IDS is the problem, CI now points at the IDS
72 of 507 specifications in 64 public IDS files carry an audit warning. The IDS model check Action now annotates each on its own line in the IDS.
-
Half the ranges taken from a Revit model's own values fail that model in IDS
The free IDS editor now offers the values a model holds. 364 of 752 ranges copied from them failed their own model, because IDS ranges take no tolerance.
-
An IDS specification doesn't have to name a class, and buildingSMART's own test files mostly don't
Our IDS editor opened buildingSMART's audit-tool files as 28% editable. Letting a specification select by attribute alone took that to 76%.
-
Revit writes Reference as a label, and an IDS check asking for an identifier fails every object
On two real Revit exports, 791 of 966 objects failed IDS checks only because of a data type. The free IDS editor now offers to drop the dataType.
-
Asking for dates a building model already holds: a date range from every value
The IDS editor now offers the range a model's dates span. With 600 doors, the earliest date was not among the 50 values on screen.
-
Two elements, one GlobalId: what 163 public IFC files hold
IFC says no two objects share a GlobalId. 3 of 163 public models break that rule, and finding them exposed a parser bug in our IFC reader.
-
Checking IFC models against IDS in a browser tab: 334 of 334 buildingSMART test cases
A free tool checks IFC models against buildingSMART IDS files in the browser. It gets all 334 official test cases right and matches IfcTester on real models.
-
An IDS file can be wrong before any model is read: auditing 334 of buildingSMART's test files
IDS Model Check now audits the IDS itself against the IFC schema. It flags 26 of buildingSMART's 27 invalid test files and none of the 307 valid ones.
-
88% of the property sets in four real IFC exports are not standard sets
The free IDS editor now opens your IFC model and offers the classes and property sets it carries. In four real exports, 347 of 395 were a project's own sets.
-
Lenght and AkousticRating: what a property set check found in 64 published IDS files
The IDS checker now audits Pset_ and Qto_ names and data types against buildingSMART's templates. In 64 public IDS files it found faults in 21.
-
Open an IDS, change it, save it: 64 public files come back asking the same thing
The free IDS editor now opens existing IDS files. All 64 public files we tried, and 187 buildingSMART test cases, write back asking for the same thing.