Is there a way to sort Min. and Max. sub-characteristics from Calypso?

[[Je...]]

.

Hi. Is there a way, besides the PiWeb sorting option, to sort Min. and Max. results for certain characteristics such as two-point distance and bilateral tolerance with two results? Can this be done from Calypso?

What I would like to do is put all of the Min. values next to each other and then all the Max. values next to each other. I would also like to occasionally only list the Min. or Max. values for two-point distance and bilateral profile w/two results.

I attempted to do this from PiWeb Reporting Plus 2022, but then several of my characteristics went crazy and either stopped populating results or stopped showing up altogether. It's confusing to assign characteristics and their order from both Calypso and PiWeb. They fight against each other. The entire "data binding" function in PiWeb is erratic.

Any ideas?

.

.

[[Da...]]

Please sign in to view this quote.

Mask LP characteristics and create multiple Min Result characteristics (don't know by heart, check around the menu), where you'd select previous LP ones.

That way you'll only get minimums.

[[Je...]]

Please sign in to view this quote.

.

Thanks, Dane. This route works fairly well as long as I use the "mark characteristic" option.

.

.

[[Mi...]]

I would alternatively suggest using a getActual() in a result Element would also work, not sure if that's any less labour intensive though.

Just a guess as I'm not at a CMM but I think the syntax would be getActual("Postcoat 2-point distance .815^Min").actual

That may not be quite right, but I have used a getActual() function to pull just a Min or Max from a 2 point Diameter.

[[Je...]]

Please sign in to view this quote.

.
Thanks, Mike. That may work even better than masking. Much appreciated!

.

[[Mi...]]

Please sign in to view this quote.

I gave the wrong syntax,

getMinActual().actual or getMaxActual().actual

I would still think you'd end up grouping and masking the 2 point distances with either method?

One caution with my suggestion - a formula in a Result element isn't enough to create the dependency. So if the feature(s) in question aren't required for any other characteristic, and you mask the 2 point distance, it won't run and then when the characteristic list tries to calculate everything you'll get an error.

So it's probably better to stick with the Min/Max characteristics, especially if other people need to run the program. But I just wanted to suggest this as an alternative that will work in some cases.