<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<div class="moz-cite-prefix">On 2020/05/12 23:51, Dirk Hohndel
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:FE5D8A9D-532A-4A55-9D9C-234E9D9C0D07@hohndel.org">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br class="">
<div><br>
<div>So here's a bad sketch:</div>
<div><br class="">
</div>
</div>
</blockquote>
<p>Not a bad sketch. In fact the concept behind it all is excellent.
One thing that I pick up here is that no filter is specified here.
How would the proposed UI below affect the present filtering
facility? Will that be replaced by a more simple filter mechanism
or will it remain unchanged? The way I read this, the existing
filter would not be changed (which would personally like). But
your idea of filter sets is not raised here at all. I assume that
this is a different topic that is not being dropped, I hope?</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:FE5D8A9D-532A-4A55-9D9C-234E9D9C0D07@hohndel.org">
<div>
<div>First you pick your values and your grouping. Most of them
are box/whiskers, the two that have just a simple # per column
could be just a plain line graph of bar chart.</div>
<div>Then you pick the grouping (i.e. x-axis)</div>
<div><br class="">
</div>
<div><img apple-inline="yes"
id="79665DBE-883D-44D6-AE92-2354DCA6BA51"
src="cid:part1.487566F5.40E7A039@zoology.up.ac.za" class=""
width="413" height="293"></div>
<div><br class="">
</div>
</div>
</blockquote>
<p>The grouping dropbox would obviously require an item "No
grouping", i.e. the full dataset. If this proposal will not affect
the existing filter mechanism, then by default the graphing will
only work on marked dives (i.e. the result of filtering using the
filter tool) *if indeed any dives have been marked by the filter*
(i.e. the filter is active). <br>
</p>
<blockquote type="cite"
cite="mid:FE5D8A9D-532A-4A55-9D9C-234E9D9C0D07@hohndel.org">
<div>
<div>Once you pick one, if needed, there's a way to specify even
further</div>
<div><br class="">
</div>
<div><img apple-inline="yes"
id="8F00D10B-653C-4AD9-A1EC-780F5E08482D"
src="cid:part2.4B198FFA.CE0C682F@zoology.up.ac.za" class=""
width="406" height="242"></div>
<div><br class="">
</div>
</div>
</blockquote>
<p>This is just a brainstorm that may help to get granularity
articulated in a useful way and the way it would work in practice.
For the granularity above, the options could be<br>
</p>
<p>Time: montly, yearly, fixed no columns</p>
<p>Trip: I cannot think of any granularity options. Stats evaluated
per trip.<br>
</p>
<p>Depth: Increments of 5m, 10m, 20m, fixed no columns</p>
<p>Duration: Increments of 10 min, 20 min, 30 min, fixed no columns</p>
<p>Temp: Increments of 2, 5 10 degrees, fixed no columns</p>
<p>All the categorical variables: I think your suggestion as for
tags below is excellent: text box.</p>
<p>For stats based on an "air/not_air" or "drysuit/no_drysuit"
basis, a mechanism would be required. A "drysuit/no_drysuit"
equipment analysis would then be specified in the textbox by e.g.
"drysuit, opposite".<br>
</p>
<blockquote type="cite"
cite="mid:FE5D8A9D-532A-4A55-9D9C-234E9D9C0D07@hohndel.org">
<div>
<div>For example, with by time with a fixed # of columns we
would create something that feels "semi reasonable" that gets
us the right number of columns.</div>
<div>You've been diving for ten years and want seven columns,
so... groups of 18 months?</div>
<div><br class="">
</div>
<div><img apple-inline="yes"
id="A42589D8-59E8-4BE5-AF42-869C17AB6D4B"
src="cid:part3.3DBC6B27.71DCDEC9@zoology.up.ac.za" class=""
width="401" height="259"></div>
<div><br class="">
</div>
<div><br class="">
</div>
<div>What am I missing? What could be better?</div>
</div>
</blockquote>
<p>I honestly cannot think of any obvious improvement. We will make
a UI designer of you yet. The # of columns above would obviously
only be active for numeric variables since it would not serve a
purpose for categorical variables such as tags.<br>
</p>
<blockquote type="cite"
cite="mid:FE5D8A9D-532A-4A55-9D9C-234E9D9C0D07@hohndel.org">
<div>
<div><br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<div class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<p class="">As far as specifying categories like
tags I like the present UI where one could
specify a number of tags to be included in the
filter, giving great flexibility. Again my
impression of such a plot possibly differs from
yours. I like your binary set idea (a set
including compared to a set excluding). But I
would more realistically often want to compare
(e.g. SAC when comparing two tags "air" and
"nitrox"), a use case which does not necessarily
imply a binary comparison because it could
compare 3 or 4 tags. Does this make sense at
all?</p>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">It makes sense for people who are able to
use sets of tags in a meaningful way - one could have
a mutually exclusive set of three tags (say, air,
nitrox, trimix) and create statistics over them. Of
course the results become "strange" if dives
potentially have multiple of those tags.</div>
<div class="">Again, to get this "mostly right" is
fairly easy. To cover all the crazy corner cases is
what's hard.</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div><img apple-inline="yes"
id="0C44A5C2-3F51-4EF5-B541-150183B2F68C"
src="cid:part4.70118537.32178D55@zoology.up.ac.za" class=""
width="420" height="261"></div>
</div>
<br>
</blockquote>
<p>Kind regards,</p>
<p>willem</p>
<p><br>
</p>
</body>
</html>
<br>
<div style="font-family:Arial,Helvetica,sans-serif"><span style="font-size:10.0pt;line-height:105%;font-family:"Segoe UI",sans-serif">This message and attachments are subject to a disclaimer.<br>
Please refer to <a href="http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf" target="_blank">http://upnet.up.ac.za/<wbr>services/it/documentation/<wbr>docs/004167.pdf</a> </span><span style="font-size:10pt;line-height:105%;font-family:Tahoma,sans-serif">for
full details.</span></div>