Home
Reply
Highlighted
Regular Contributor
Posts: 58
0
Accepted Solution

api_fix_check_problems

Hello,

 

It is said that api_fix_check_problems attempts to fix the following problems:

"The insanity IDs for which a fix will be attempted are: CRV_BAD_FITOL, SURF_BAD_FITOL, CURVE_APPROX_OVERCLAMPED, CURVE_MISSING_DISC_INFO, and SURF_MISSING_DISC_INFO"

(I'm referring to the documentation:

https://doc.spatial.com/get_doc_page/qref/ACIS/html/group__ACISCHECKING.html#gabd6c6d1c0e7c73aac65a4...)

The list is perhaps outdated. What's the current state of api_fix_check_problems, were some other insanities added?

I'm specifically interested in the following issues:

1. pcurve location != coedge location

2. internal position on coedge off face

Thank you!

 

Spatial Employee
Posts: 151
0

Re: api_fix_check_problems

Hi 

 

This API is mostly a historical curiousity I think.  I don't advise using it.

 

The errors you mentioned occur because the part is not tolerant but it should be.  Use api_tolerize_entity for this.