Changing data in a "hit array"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Changing data in a "hit array"

    I have been struggling with the elimination of outliers for some time. The PC-DMIS standard method based on a certain amount of sigma, has proven unworkable for me. So I have devised another method that looks through the hit array and finds the outliers. Now that was the easy task. But here comes the problem:

    When I know that one of the values is a clear outlier (I know the index and I know what value I want to make it), how do I load a corrected number into that specific loaction?

    Here is an example of code that did NOT work:

    Code:
    ASSIGN/SIMULATED_DATUM_E.HIT[1].Z = 0
    How would I load 0 into the first Z location of this hit array??? ??



    Jan.
    ***************************
    PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
    Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

  • #2
    scripting

    Jan, I do have a BASIC script or two that works with scan features to perform this sort of task. It was written for a specific purpose, and I can't send you the whole collection of files but I'd e glad to see if I can break out something that might help you.

    Here's a synopsis of it -

    After scanning data into one feature, the script "processes" the data and pumps it into another (pre-existing) scan feature. The trick is that the program execution has already passed by this second feature, but because it had no hits at the time, it was just ignored. The filtering "black box" is up to you, but you might be interested in the code pieces that do the reading and writing. . .

    Comment


    • #3
      Post it here plese. I'd love to see this solution.
      <internet bumper sticker goes here>

      Comment


      • #4
        Originally posted by Don Ruggieri
        Jan, I do have a BASIC script or two that works with scan features to perform this sort of task. It was written for a specific purpose, and I can't send you the whole collection of files but I'd e glad to see if I can break out something that might help you.

        Here's a synopsis of it -

        After scanning data into one feature, the script "processes" the data and pumps it into another (pre-existing) scan feature. The trick is that the program execution has already passed by this second feature, but because it had no hits at the time, it was just ignored. The filtering "black box" is up to you, but you might be interested in the code pieces that do the reading and writing. . .

        Wow, I had hoped it was simple....

        But please, post some code that is applicable. I'd love to try it. I'd also like to take a look at the filter code, if you have it...


        Thanks Don!
        ***************************
        PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
        Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

        Comment

        Related Topics

        Collapse

        Working...
        X