Dealing with the last point first. As the comparison was for a CLI, the bounding box are always the same as its fixed pitch fonts I'm dealing with. I did consider trying to grab bitmaps and determine it that way, but given that the use is for human perception rather than machine perception that is difficult. Even dealing with monochrome becomes dependant not just on the number of pels that are on relative to those off, it also depends on the concentration of those pels. It further depends on the way the pels in adjacent cells intereact.

I found that but not trying to hard to judge it, but rather reacting to the obvious choices as appropriate and opting for "the same" whenever I didn't immediately perceive a difference, I ended up with a fairly good result. It probably wasn't perfect, but then no lives were dependant upon the accuracy of the conclusion:) For my purposes I only needed to grade them approximately as I then chose the two from the ends, space and #, and then 6 roughly evenly spaced throughout the range.

I did find that it helped if I reduced the size of the font to the smallest available on my system (5pt Lucida TT or a 4x6 raster) as when I could no longer make out what the chars were and stopped trying to decide which was darker on the basis of logic and just went with my visual perception.

Your right that humans aren't consistant, but that would always be true, regardless of the method used to marshall and record the decisions made.

I have not been able to create a seg fault even when I just deliberately tried to make inconsistant decisions. I am unsure as to how that would occur? It's not like the sort would 'remember' my decisions, It's only ever comparing two values at a time?

YMMV as they say:)... I wouldn't rely upon it for anything important, but it served it purpose.

Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.

In reply to Re: Re: Really slow sort, but useful. by BrowserUk
in thread Really slow sort, but useful. by BrowserUk

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.