hexagon logo

"Default" Math Vs "Legacy"?

What are we calling the new default Geo-Tol math? "New Math"? "Default Math"?
I remember this gun fight a loooong time ago, it ended up bad for Hexagon and us also.
what I mean is:
The "New Math" best fits a little too aggressive for me compared to "Legacy". Last time I had reports coming out with perfect true position our customer Lockheed Martin mopped the floor with Pc-Dmis and started the whole ISO Best-Fit shootout, disallowing us to use Pc-Dmis best fit algorithms. The "New Math" best fits also. Here is a comparison:



What do you think?
and can we come up with a disparaging term like "New Math" other than "Geo-Tol"? or "Geo out-of Tol"?

thx
Parents
  • Dear Illustrious Programmers and other lecherous Forum Members,


    I sincerely appreciate ALL the inputs to this conversation, while emotional and overdramatic, empirical and mildly dramatic and threatening: (Oooo000000000000000ooohh Nooooooooo000000000000000000, I LUUUUUUUUUUUUUUUUUUV drama!) I really feel we've popped the cherry on this topic, and before you all kick me out of bed, I'd like to ask one more question of us.

    I am mildly enamored with the "newmath" unrelated actual mating envelope (UAME) and the local and global Least Squares Algorithms, I empirically repair to least squares because in my understanding, we can only with any certainty mathematically deduce the middle of something and that's it. But, I work for a living, and I'm only as valuable as I can be accurate in my measurements period. Nobody pays me *** for guessing.
    i've tried my hardest to understand the gobbly-gook here:

    https://docs.hexagonmi.com/pcdmis/2020.2/en/helpcenter/mergedProjects/core/geometric_tolerances/Evaluating_Size_with_the_Geometric_Tolerance_Command.htm

    But I want to know from the guys who somehow survive this mess day in and day out:

    How do you use these options when probing diameters over 1.0000 with tolerances below .0005 total on global machines?
    What combinations do you use to homogenize and harmonize UAME, LS Local Size without datum shift to give clear, concise and stable direction to machine correction and set-ups?

    Off-topic:
    (I woke up this morning wearing all my clothes from yesterday except for my shirt, my girlfriend woke me up and said: "Baby, you need to get to work now, you're late." I asked her: "What happened, what did I do last night?" and with a far away glassy eyed stare and a smile she said: "I'll tell you later." Wink

    Sincerely,

    SPace-Cowboy
    Gabriel
  • for the record, Calypso's strategies are still an averaging estimation of the data hits, just like PCDMIS's options. it's simply a different software.
    In fact, calypso's default strategy is also least squares. it's industry standard to use the median output of hit point variation.
    https://carl-zeiss-industrial-metrology-llc.helpjuice.com/en_US/calypso/algorithms

    I will absolutely agree that PCDMIS's Gaussian and hit-filtering strategies are garbage, and historically useless... but they have been working on improving this function.

    In any case, you can extrapolate hit data and use excel, matlab, minitab etc software to help you determine if the PCDMIS strategies are correct.
Reply Children
No Data