From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: time profiling and other meta-analytic commands (was automatic clocking) Date: Sun, 23 Aug 2009 15:20:24 -0700 Message-ID: <20524da70908231520w2ac6e3ceqfe3b16be02e72b9a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfLQN-0003qV-NV for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 18:20:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfLQI-0003qI-6J for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 18:20:30 -0400 Received: from [199.232.76.173] (port=47460 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfLQH-0003qF-R9 for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 18:20:25 -0400 Received: from mail-iw0-f185.google.com ([209.85.223.185]:62113) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfLQH-0002t7-FE for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 18:20:25 -0400 Received: by iwn15 with SMTP id 15so732947iwn.14 for ; Sun, 23 Aug 2009 15:20:24 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode My idea, which might or might not meet the automatic clocking thread's OP's need, should be called time profiling to avoid confusion. The idea is to figure out where in the outline hierarchy you spend your time, in an approximate fashion, much like profiling code. This is done - without polluting the numerous entries with LOGBOOK drawers - without the need to clock in and out of hundreds of tasks - with exheritance (that is, times get summed up the hierarchy) It is only one example of a general class of possible commands that do meta-analysis of the way you use org. Other members of this class might include 1) rate measurement, where we display how rapidly you add tasks vs. dispose of them on average over a period of time. For example, if you add 10 tasks per day, but only mark 5 tasks per day as done, your rate is 0.5. This could even be charted. X axis is time. 2) design element utilization, where we display, numerically, how often you use each todo keyword, tag, priority, etc. If you almost never use a todo keyword, it might or might not be useful. You might discover that you are being lazy by marking everything TODO instead of using more specific todo keywords. 3) todo state transition utilization. Draw a nice graph-theoretical chart. 4) space profiling, where we do something like the "du" command in Unix, counting the subtrees that are large recursively. 5) linting, where we check for integrity of the outline tree, checking that all nodes have parents, aligning tags, enforcing indentation preferences, etc. -- Myalgic encephalomyelitis causes death (Jason et al. 2006) and severe suffering. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm