A written description of what the data represents might help us understand the data and perhaps offer a solution to your described problem--assuming one exists.

The best interpretation I could muster from your description is that the data lines:

182 196 777 180 197 777

Means that artifact 182 was found in a higher(or maybe lower, I couldn't decide?) strata than artifact 196,which in turn was in a higher strata than artifact 777. And that a similar relationship exists between the artifacts in the second line. But although artifacts 196 and 197 where definitely both higher than artifact 777, it does not mean they were both at the same level, nor illustrate anything about their relative depths. Same goes for artifacts 182 and 180.

So from those two lines alone, any of the following (plus many other), relative positionings is possible:

182 180 182 180 182 180 197 196 196 197 196 182 180 197 196 197 777 777 777 777

I first thought the purpose of the code was to try and 'sort' the artifacts from top to bottom be resolving all the relative positionings, but the form of the output doesn't seem to bear that out. If that were the case, it would appear to put far too many artifacts at one level?

My next thought was that the data indicated a physical overlap in the x/y plane. Ie. That some part of artifact 196 physically overlays some part of artifact 777. And the same for 197.

And that the purpose was to say that all these artifacts were in one part of the dig, (one spatial grouping), and these were grouped in another part of the dig. And there was no overlap between any of the items within those two (or more) groupings.

That seems more likely, but it would be easier to understand if you said up front what the data actually means.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Determine group membership for partial sequences by BrowserUk
in thread Determine group membership for partial sequences by GrandFather

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.