hexagon logo

2022.1SP6 Parallelism issue

I have 2 planes, PL1 is datum A (primary using minimax), and PL2 constructed from 7 basic scan/circle/plane. (least square, but it shouldn't change anything !)
Using geotol, it gives 7,1 µm
using legacy, it gives 35,1 µm
using assignments (ASSIGN/V1=DOT(PL2.HIT[1..PL2.NUMHITS].XYZ-PL1.XYZ,PL1.IJK) , then ASSIGN/V2=MAX(V1)-MIN(V1)), it gives 36,1 µm.
Then, constructing 7 planes from scans and construct a plane from their centroids, it gives about 8 µm (so I'm wondering if geotol uses them to calculate instead of hits ?)

Don Ruggieri , neil.challinor
Parents
  • I tried this as well [..] and it did not work, you can see that when you use the [..] with out the numhits the Theo and Actl do not populate with values ?
  • neil.challinor But the spaces are in the "destination" feature (the feature created from the NUMHITS features), there are no spaces in the NUMHITS source features. So, if you change the syntax to [1..FEATURENAME.NUMHITS], there will be no issues, but if you keep the syntax as [..], it will not work (while keeping the spaces in the feature name).

    I'd assume that removing the spaces in the feature name would make it work too.

    As always, thanks for the update!
Reply
  • neil.challinor But the spaces are in the "destination" feature (the feature created from the NUMHITS features), there are no spaces in the NUMHITS source features. So, if you change the syntax to [1..FEATURENAME.NUMHITS], there will be no issues, but if you keep the syntax as [..], it will not work (while keeping the spaces in the feature name).

    I'd assume that removing the spaces in the feature name would make it work too.

    As always, thanks for the update!
Children
No Data