Not calculated revisited...

[[Jo...]]

Ok so I thought I had everything figured out with my "not calculated" items, but I ran into a situation with conditions inside a program and caused the report to have "not calculated" items because it read the skipped conditions as being "not" calculated.   Does anyone know the error code that calypso uses to show on the old custom printout if a "feature" is not calculated correctly?  I attached a screen shot of a custom report with the not calculated value. 

My thinking is if i knew what it uses to make this error code, i could then set it to a variable to be registered on PiWeb.. and skip  my other routine that is counting the conditions now.

[[Pi...]]

It is a little late. But if you want to have features measured regardless your conditions inside inspection plan you can add "dummy" extra alignments and placed then on top of the program and if require add them to the miniplan. This method will "enforce" measurement features that are "excluded" later by conditions. If you still have issues with this even when you are 100% sure that you made measurement - try to check your filters and outliers as they might "kill" to many points. If you working with cones then you might re-think measuring strategy as in specific situations you might have issues with very short cones, or with cones with huge/very small cone angles.

 

I hope that can help.