Calypso uses 99,999 as a value for missing points.

[[An...]]

I am sorting about 60 measurements taken over 3 years and we have added a few characteristics in the last few months. The problem I am having is Calypso will just use 99,999 as values instead of a null value which really throws off max value, average, std dev. Is there a way to remove outliers in PiWeb when looking at lots of measurements?

[[Ha...]]

I'm guessing that, in addition to adding characteristics to an established measurement, features were also added as well. Since the new features were only measured within the last several months, any evaluations of their characteristics beyond that timeframe will show 99999 as a value.

If you have PiWeb Reporting Plus, I recommend either limiting the trend to the most recent measurements for the added characteristics in the measurement plan, or by direct selection. The same can be done in PiWeb Designer as well (link below on how to select measurements for table or trend protocol templates).

https://portal.zeiss.com/knowledge-base?id=499938

[[Ke...]]

Joe,
Am I understanding correctly that PIWeb, if there are characteristics added at a later date, automatically fills in 99999 for those characteristics for any measurements take prior to the addition of the characteristic? I understand why that would be needed to prevent issues, but that is really good to know, thank you.

[[Ha...]]

Please sign in to view this quote.

It specifically will do this for features added at a later date. Thus, when a subsequent evaluation is done for the measurement plan, the value will be 99999 for characteristics of the added feature. Characteristics added to already established features will display nothing (at least from my testing in Calypso 2024).