{"id":42,"date":"2007-09-16T22:44:12","date_gmt":"2007-09-17T03:44:12","guid":{"rendered":"http:\/\/www.visophyte.org\/blog\/2007\/09\/16\/python-dev-mailman-archive-thread-arc-visualizations\/"},"modified":"2009-04-01T08:19:59","modified_gmt":"2009-04-01T13:19:59","slug":"python-dev-mailman-archive-thread-arc-visualizations","status":"publish","type":"post","link":"https:\/\/www.visophyte.org\/blog\/2007\/09\/16\/python-dev-mailman-archive-thread-arc-visualizations\/","title":{"rendered":"python-dev mailman archive thread-arc visualizations"},"content":{"rendered":"<p>What&#8217;s new?  Mailman archive processing!  Bezier segmenting for more accurate arcs (<a href=\"http:\/\/www.spaceroots.org\/documents\/ellipse\/\">thank you Luc Masonobe<\/a>)! Pseudo-<a href=\"http:\/\/www.research.ibm.com\/remail\/threadarcs.html\">thread-arcs<\/a>! (Actual thread arcs as visible on the whoa-awesome-but-why-aren&#8217;t-you-released-software <a href=\"http:\/\/www.research.ibm.com\/remail\/\">ReMail<\/a> project would seem to more practically squash ridiculously-large arcs and of course leverage the other side.)<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2007\/09\/python-dev-july-2007-threadarc-assembled.png\" alt=\"python-dev-july-2007-threadarc-assembled.png\" \/><\/p>\n<ul>\n<li>Node colors are per-author.  The middle bottom thread demonstrates the need for a smarter distinct color logic, as I&#8217;m pretty confident that thread isn&#8217;t the result of one person with multiple personalities.<\/li>\n<li>Nodes are sequenced time-wise from left-to-right with uniform (pixel-based) spacing.  I tried placing them by time, but things clump up pretty uselessly.  Non-linear time scaling is on my list.<\/li>\n<li>Arc colors are based on the subject, whereas reconstruction is based on the headers.  As such, arc colors in a thread may change if someone changes the subject.<\/li>\n<li>Arc width is constant, though I was entertaining varying it based on the amount of new content in each e-mail.  Of course, there&#8217;s always knobs to tweak.<\/li>\n<\/ul>\n<p>Please note that the above image is actually the result of re-arranging the contents of two separate images; the layout currently used just stacks them all vertically with a (dynamic) uniform spacing.  For this reason, the rightmost threads are actually from a separate run where I set the &#8216;chaos&#8217; filter with a much higher bar.  Oh, and those are threads from the July 2007 python-dev archive, although without labeling you have no reason to believe me.<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/www.visophyte.org\/blog\/wp-content\/uploads\/2007\/09\/python-dev-2007-threadarc-chaos200.png\" alt=\"python-dev-2007-threadarc-chaos200.png\" \/><\/p>\n<p>And this is the result of sucking up January-July 2007, filtering on threads with a &#8216;chaos&#8217; greater than 200.  (&#8216;chaos&#8217; being an arbitrary and arguably incorrect term for the total distance of all nodes from their parent (less one).  So a thread where every message is just a response to the one that chronologically preceded it will have a chaos of 0.  A thread where every message is a response to the message before the one that chronologically preceded it will have a chaos of (n &#8211; 2) where n is the number of messages.  Apply algebra, rinse, and repeat.<\/p>\n<p>I&#8217;m going to try and get this going with Thunderbird reasonably soon, but it might take longer than I&#8217;d hope.  Thunderbird w\/pyxpcom didn&#8217;t build clean on my amd64-arch laptop, chronicle-recorder&#8217;s valgrind crashes on amd64, and the like means some busywork on the horizon.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What&#8217;s new? Mailman archive processing! Bezier segmenting for more accurate arcs (thank you Luc Masonobe)! Pseudo-thread-arcs! (Actual thread arcs as visible on the whoa-awesome-but-why-aren&#8217;t-you-released-software ReMail project would seem to more practically squash ridiculously-large arcs and of course leverage the other &hellip; <a href=\"https:\/\/www.visophyte.org\/blog\/2007\/09\/16\/python-dev-mailman-archive-thread-arc-visualizations\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[5,4],"tags":[41,39],"class_list":["post-42","post","type-post","status-publish","format-standard","hentry","category-email","category-visualizing","tag-mailman","tag-visophyte"],"_links":{"self":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/42","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/comments?post=42"}],"version-history":[{"count":2,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/42\/revisions"}],"predecessor-version":[{"id":239,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/42\/revisions\/239"}],"wp:attachment":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/media?parent=42"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/categories?post=42"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/tags?post=42"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}