From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raymond Zeitler Subject: org-clock-rounding-minutes -- non-zero value can cause double clocking Date: Fri, 8 Mar 2019 18:33:35 +0000 (UTC) Message-ID: <1752809487.2399229.1552070015695@mail.yahoo.com> References: Reply-To: Raymond Zeitler Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2399228_1254167247.1552070015694" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51935) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2KJW-0007PT-GU for emacs-orgmode@gnu.org; Fri, 08 Mar 2019 13:33:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h2KJV-0008Br-Ky for emacs-orgmode@gnu.org; Fri, 08 Mar 2019 13:33:46 -0500 Received: from sonic307-9.consmr.mail.ne1.yahoo.com ([66.163.190.32]:33106) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h2KJU-000871-QR for emacs-orgmode@gnu.org; Fri, 08 Mar 2019 13:33:45 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org ------=_Part_2399228_1254167247.1552070015694 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable There is a problem when org-clock-rounding-minutes is non-zero, say N.=C2= =A0 The problem is that the=C2=A0clockin-time of a task can be N less than = the clockout-time=C2=A0of the previous task at certain times.=C2=A0 Thus, c= lock reports can show an extra N minutes total time for each occurrence of = this effect. Consider this. Set=C2=A0org-clock-rounding-minutes to 6. (This allows for tracking time in= 0.1 hour increments.) Create an org file with two tasks: * Tasks** TODO Foo** TODO Bar Clock into Task Foo at, say, 12:54 plus or minus 2 minutes.=C2=A0 Its LOGBO= OK will show the expected 12:54 timestamp. Clock into Bar at 12:57, which is halfway between 0.90th hour and 1.00th ho= ur. Result, the clockout time for Foo is rounded up.=C2=A0 But the clockin time= for Bar is rounded *down*.=C2=A0 Thus, two tasks have started at the same = time. * Tasks** TODO Foo=C2=A0 =C2=A0:LOGBOOK:=C2=A0 =C2=A0CLOCK: [2019-03-08 Fri= =C2=A012:54]--[2019-03-08 Fri 13:00] =3D>=C2=A0 0:06=C2=A0 =C2=A0:END:** TO= DO Bar=C2=A0 =C2=A0:LOGBOOK:=C2=A0 =C2=A0CLOCK: [2019-03-08 Fri=C2=A012:54]= =C2=A0 =C2=A0:END: So when I use org-mode to track time for my weekly timesheet, it will repor= t that my total clocked time for any given day is several minutes more than= the time I've been at work! I expect that the clockin time of Bar will be the same as the clockout time= of Foo. Is there another variable I need to set in order to enforce clockin-time=3D= clockout-time? org-version returns 9.1.2-37 - Ray ------=_Part_2399228_1254167247.1552070015694 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There is a problem when= org-clock-rounding-minutes is non-zero, say N.  The prob= lem is that the clockin-time of = a task can be N less than the clockout-time of the previ= ous task at certain times.  Thus, clock reports can show an extra N mi= nutes total time for each occurrence of this effect.

Consider this.

Set org-clock-roundin= g-minutes to 6. (This allows for tracking time in 0.1 hour increments.)

Create an org file with two= tasks:

* Tasks
** TODO Foo
** TODO Bar

Clock= into Task Foo at, say, 12:54 plus or minus 2 minutes.  Its LOGBOOK wi= ll show the expected 12:54 timestamp.

Clock into B= ar at 12:57, which is halfway between 0.90th hour and 1.00th hour.

Result, the clockout time for Foo is rounded up.  But= the clockin time for Bar is rounded *down*.  Thus, two tasks have sta= rted at the same time.

<= /div>
* = Tasks
** TODO Foo
   :LOGBOOK:
&= nbsp;  CLOCK: [2019-03-08 Fri 12:54]--[2019-03-08 Fri 13:0= 0] =3D>  0:06
   :END= :
** TODO Bar
   :LOGBOOK:
 = ;  CLOCK: [2019-03-08 Fri 12:54]
   :END:

So when I use org-mode to track time for my weekly tim= esheet, it will report that my total clocked time for any given day is seve= ral minutes more than the time I've been at work!

I expect that the clockin time of Bar will be the same as the clockout ti= me of Foo.

Is there another variable I need to set= in order to enforce clockin-time=3Dclockout-time?

org-version returns 9.1.2-37

- Ray

=



------=_Part_2399228_1254167247.1552070015694--