<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 12, 2020, at 10:30 PM, Arjun Salyan <<a href="mailto:arjun@macports.org" class="">arjun@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div dir="auto" class="">Hi Craig,<br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Thank you. You make a valid point regarding the possible distortion due to weekly submissions being bundled to calculate monthly charts. </div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">But what we are seeing here is a known issue with the query that calculates this chart.</div><div dir="auto" class=""><div class=""><a href="https://github.com/macports/macports-webapp/issues/79" target="_blank" class="">https://github.com/macports/macports-webapp/issues/79</a></div><div class=""><br class=""></div><div dir="auto" class="">The current query has a limitation. Let’s say we receive two submissions from a user within one month. One has port version X.1 and the other has upgraded version X.2, then this query counts that user as using both the versions and not just the latest one. This is the cause for the sudden jump in Mar 2020. This problem is only with the "versions vs month" chart and should be fixed soon. Rest all charts, including "installations by month" display accurate information (<a href="https://ports.macports.org/port/gnuplot/stats?days=365" class="">https://ports.macports.org/port/gnuplot/stats?days=365</a>).</div><div dir="auto" class=""><br class=""></div><div class="">Thank you for the percentage suggestion. I am just wondering the right way to display that information graphically.</div><div class=""><br class=""></div><div class="">I was trying to combine "installations by months" and "versions by month", but it turns out they would be better separate.</div><div class=""><br class=""></div><div class="">Thank you</div></div></div>
</div>
<br class=""><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/bb7b6eb374d7a98273ee16d1177dbea11155bccc.png?u=4480800"></div>
</div></blockquote><br class=""></div><div>The following is a quick mockup of how versions over time might be reported:</div><div><br class=""></div><a href="https://drive.google.com/file/d/1piEDpd_rq5xnSMAgEsvLO5eu9uu70OpV/view?usp=sharing" class="">https://drive.google.com/file/d/1piEDpd_rq5xnSMAgEsvLO5eu9uu70OpV/view?usp=sharing</a><div class=""><br class=""></div><div class="">To display percentages, I don’t think we need the ‘count distinct’. Suppose only a single system is reporting that it uses a particular port and that port is updated during the month. Suppose further, that the first two reports in the month from that single system say it is using version 1.0 and the last two say it is has version 1.1 installed. Given the way we collect stats, I think it would be accurate to report usage as 50% for each of the versions of the port for that month. Over the course of the month, that was what was reported.</div><div class=""><br class=""></div><div class="">Either that or only use the last report for the month and have the date displayed as the last day of each month.</div><div class=""><br class=""></div><div class="">Craig</div></body></html>