search

ifcquery / ifcplusplus

IfcPlusPlus is an open source C++ class model, as well as a reader and writer for IFC files in STEP format. Features: Easy and efficient memory management using smart pointers. Parallel reader for very fast parsing on multi-core CPU's. Additionally, there's a simple IFC viewer application, using Qt and OpenSceneGraph. It can be used as starting point for all kinds of applications around the open building model standard IFC.
http://www.ifcquery.com
MIT License
589 stars 211 forks source link

Feature Request: add STEP numbers next to each fail in the Read/Write IFC Tab. #19

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I currently get an anonymized list of errors in the Read/Write IFC tab, like:

Error: convertIfcBooleanOperand problems in extrude: poly_data->points.size() 
!= 2*polygonal_boundary.size()
convertIfcBooleanOperand problems in extrude: poly_data->points.size() != 
2*polygonal_boundary.size()
convertIfcBooleanOperand problems in extrude: poly_data->points.size() != 
2*polygonal_boundary.size()
convertIfcBooleanOperand problems in extrude: poly_data->points.size() != 
2*polygonal_boundary.size()
convertIfcBooleanOperand problems in extrude: poly_data->points.size() != 
2*polygonal_boundary.size()
...

By knowing the STEP numbers, where each fail occurs, I could extract only the 
offending IFC snippets and attach them to future logs.

Thanks

Original issue reported on code.google.com by ivano....@gmail.com on 5 Aug 2014 at 2:43

GoogleCodeExporter commented 9 years ago 
I would recommend to use a debugger. Then you can easily get the STEP id and 
other information about the concerning object.

Original comment by fabian.g...@gmail.com on 5 Aug 2014 at 2:49

GoogleCodeExporter commented 9 years ago 
Having the STEP ids beside each error would help narrowing down what part of 
the IFC file is causing the issue. But no worries, I will add them myself to my 
local IFC++ codebase if it's a problem.

Original comment by ivano....@gmail.com on 5 Aug 2014 at 3:36

GoogleCodeExporter commented 9 years ago 
I agree that appending the entity id to the error messages makes sense. It is 
now added to the error message above and others in SolidModelConverter. If you 
find other error messages without entity id, please let me know.

Original comment by fabian.g...@gmail.com on 6 Aug 2014 at 9:53

GoogleCodeExporter commented 9 years ago 
Sure, will do. Thank you kindly

Original comment by ivano....@gmail.com on 6 Aug 2014 at 10:29

GoogleCodeExporter commented 9 years ago 
More on this enhancement request : please find the following commit 
https://github.com/VTREEM/IFCPlusPlus2/commit/2eefb0031a21e1f1d801ce2b787dc57966
12ce43 :
"Report CSG errors in the err stream even when no exception has been raised."

Original comment by sylvain....@vtreem.com on 8 Sep 2014 at 4:40