* clocktable: maximum level 0 does not only avoid listing items but also does not calculate items @ 2010-07-13 9:21 Rainer Stengele 2010-07-21 14:24 ` Carsten Dominik 0 siblings, 1 reply; 12+ messages in thread From: Rainer Stengele @ 2010-07-13 9:21 UTC (permalink / raw) To: emacs-orgmode Hi all! lately I use the marvelous clocktables a lot... For toplevel clocktables which just sum up "all" I use ":maxlevel 0" The manual reads :maxlevel Maximum level depth to which times are listed in the table. which I misunderstood. I understood: an unlisted item does not mean that its time is not added! But it looks like ":maxlevel 0" does not add everything up. Ok, maybe the manual is a bit misleading here. How can I get a clocktable without any details which simply adds up everything in the scope? BTW, the ":stepskip0" parameter does not seem to be included in the manual. Rainer ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-07-13 9:21 clocktable: maximum level 0 does not only avoid listing items but also does not calculate items Rainer Stengele @ 2010-07-21 14:24 ` Carsten Dominik 2010-07-22 7:16 ` Rainer Stengele 0 siblings, 1 reply; 12+ messages in thread From: Carsten Dominik @ 2010-07-21 14:24 UTC (permalink / raw) To: Rainer Stengele; +Cc: emacs-orgmode On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: > Hi all! > > lately I use the marvelous clocktables a lot... > > For toplevel clocktables which just sum up "all" I use ":maxlevel 0" > > The manual reads > > :maxlevel Maximum level depth to which times are listed in the > table. > > which I misunderstood. > I understood: an unlisted item does not mean that its time is not > added! > But it looks like ":maxlevel 0" does not add everything up. I cannot reproduce this, :maxlevel 0 works for me. > > Ok, maybe the manual is a bit misleading here. > > > > How can I get a clocktable without any details which simply adds up > everything in the scope? > > BTW, the ":stepskip0" parameter does not seem to be included in the > manual. It is in the manual. - Carsten > > > Rainer > > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-07-21 14:24 ` Carsten Dominik @ 2010-07-22 7:16 ` Rainer Stengele 2010-07-22 7:47 ` Carsten Dominik 2010-10-26 11:30 ` Carsten Dominik 0 siblings, 2 replies; 12+ messages in thread From: Rainer Stengele @ 2010-07-22 7:16 UTC (permalink / raw) Cc: emacs-orgmode Am 21.07.2010 16:24, schrieb Carsten Dominik: > > On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: > >> Hi all! >> >> lately I use the marvelous clocktables a lot... >> >> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >> >> The manual reads >> >> :maxlevel Maximum level depth to which times are listed in the table. >> >> which I misunderstood. >> I understood: an unlisted item does not mean that its time is not added! >> But it looks like ":maxlevel 0" does not add everything up. > > > I cannot reproduce this, :maxlevel 0 works for me. > >> >> Ok, maybe the manual is a bit misleading here. >> >> >> >> How can I get a clocktable without any details which simply adds up everything in the scope? >> >> BTW, the ":stepskip0" parameter does not seem to be included in the manual. > > It is in the manual. > > - Carsten >> >> >> Rainer >> >> >> Carsten, maybe I misunderstood. 1. Without maxlevbel I get I get #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" Clock summary at [2010-07-22 Do 09:07] | File | L | Timestamp | Headline | Time | | | |-------------------+---+---------------------+----------------+----------+--------+--------| | | | Timestamp | *Total time* | *327:51* | | | ... with :maxlevel 0 I get #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" Clock summary at [2010-07-22 Do 09:11] | File | L | Timestamp | Headline | Time | |------+---+-----------+--------------+----------| | | | Timestamp | *Total time* | *232:17* | |------+---+-----------+--------------+----------| #+END: I would like to get the same results! Is ":maxlevel 0" intended to not include the sublevel clocks? If not how can I debug this? - Rainer ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-07-22 7:16 ` Rainer Stengele @ 2010-07-22 7:47 ` Carsten Dominik 2010-10-07 8:41 ` Rainer Stengele 2010-10-26 11:30 ` Carsten Dominik 1 sibling, 1 reply; 12+ messages in thread From: Carsten Dominik @ 2010-07-22 7:47 UTC (permalink / raw) To: Rainer Stengele; +Cc: emacs-orgmode On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > Am 21.07.2010 16:24, schrieb Carsten Dominik: >> >> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >> >>> Hi all! >>> >>> lately I use the marvelous clocktables a lot... >>> >>> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >>> >>> The manual reads >>> >>> :maxlevel Maximum level depth to which times are listed in the >>> table. >>> >>> which I misunderstood. >>> I understood: an unlisted item does not mean that its time is not >>> added! >>> But it looks like ":maxlevel 0" does not add everything up. >> >> >> I cannot reproduce this, :maxlevel 0 works for me. >> >>> >>> Ok, maybe the manual is a bit misleading here. >>> >>> >>> >>> How can I get a clocktable without any details which simply adds >>> up everything in the scope? >>> >>> BTW, the ":stepskip0" parameter does not seem to be included in >>> the manual. >> >> It is in the manual. >> >> - Carsten >>> >>> >>> Rainer >>> >>> >>> > > > Carsten, > > maybe I misunderstood. > > > 1. Without maxlevbel I get I get > > #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp > t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" > Clock summary at [2010-07-22 Do 09:07] > > | File | L | Timestamp | Headline | > Time | | | > |-------------------+---+---------------------+---------------- > +----------+--------+--------| > | | | Timestamp | *Total time* | > *327:51* | | | > ... > > > > with :maxlevel 0 I get > > > #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" > "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend > "<2010-07-31 Sa 23:55>" > Clock summary at [2010-07-22 Do 09:11] > > | File | L | Timestamp | Headline | Time | > |------+---+-----------+--------------+----------| > | | | Timestamp | *Total time* | *232:17* | > |------+---+-----------+--------------+----------| > #+END: > > > I would like to get the same results! Indeed, this looks wrong. Unfortunately I don't have time to look at this before my vacation (starting tomorrow....) :( Please remind me when I get back. - Carsten > Is ":maxlevel 0" intended to not include the sublevel clocks? > If not how can I debug this? > > > - Rainer - Carsten ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-07-22 7:47 ` Carsten Dominik @ 2010-10-07 8:41 ` Rainer Stengele 0 siblings, 0 replies; 12+ messages in thread From: Rainer Stengele @ 2010-10-07 8:41 UTC (permalink / raw) Cc: emacs-orgmode Am 22.07.2010 09:47, schrieb Carsten Dominik: > > On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > >> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>> >>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>> >>>> Hi all! >>>> >>>> lately I use the marvelous clocktables a lot... >>>> >>>> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >>>> >>>> The manual reads >>>> >>>> :maxlevel Maximum level depth to which times are listed in the table. >>>> >>>> which I misunderstood. >>>> I understood: an unlisted item does not mean that its time is not added! >>>> But it looks like ":maxlevel 0" does not add everything up. >>> >>> >>> I cannot reproduce this, :maxlevel 0 works for me. >>> >>>> >>>> Ok, maybe the manual is a bit misleading here. >>>> >>>> >>>> >>>> How can I get a clocktable without any details which simply adds up everything in the scope? >>>> >>>> BTW, the ":stepskip0" parameter does not seem to be included in the manual. >>> >>> It is in the manual. >>> >>> - Carsten >>>> >>>> >>>> Rainer >>>> >>>> >>>> >> >> >> Carsten, >> >> maybe I misunderstood. >> >> >> 1. Without maxlevbel I get I get >> >> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >> Clock summary at [2010-07-22 Do 09:07] >> >> | File | L | Timestamp | Headline | Time | | | >> |-------------------+---+---------------------+----------------+----------+--------+--------| >> | | | Timestamp | *Total time* | *327:51* | | | >> ... >> >> >> >> with :maxlevel 0 I get >> >> >> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >> Clock summary at [2010-07-22 Do 09:11] >> >> | File | L | Timestamp | Headline | Time | >> |------+---+-----------+--------------+----------| >> | | | Timestamp | *Total time* | *232:17* | >> |------+---+-----------+--------------+----------| >> #+END: >> >> >> I would like to get the same results! > > Indeed, this looks wrong. > > Unfortunately I don't have time to look at this before my vacation (starting tomorrow....) :( > Please remind me when I get back. > > - Carsten > Hi Carsten, this is still open, I just tested. I feel like this is a near to "major" bug because it will simply "vary" your (work) time calculation if you choose different maxlevels. - Rainer ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-07-22 7:16 ` Rainer Stengele 2010-07-22 7:47 ` Carsten Dominik @ 2010-10-26 11:30 ` Carsten Dominik 2010-10-26 13:53 ` Rainer Stengele 2010-10-30 16:18 ` Bernt Hansen 1 sibling, 2 replies; 12+ messages in thread From: Carsten Dominik @ 2010-10-26 11:30 UTC (permalink / raw) To: Rainer Stengele, Bernt Hansen; +Cc: org-mode List Hi Rainer, hi Bernt, On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > Am 21.07.2010 16:24, schrieb Carsten Dominik: >> >> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >> >>> Hi all! >>> >>> lately I use the marvelous clocktables a lot... >>> >>> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >>> >>> The manual reads >>> >>> :maxlevel Maximum level depth to which times are listed in the >>> table. >>> >>> which I misunderstood. >>> I understood: an unlisted item does not mean that its time is not >>> added! >>> But it looks like ":maxlevel 0" does not add everything up. >> >> >> I cannot reproduce this, :maxlevel 0 works for me. >> >>> >>> Ok, maybe the manual is a bit misleading here. >>> >>> >>> >>> How can I get a clocktable without any details which simply adds >>> up everything in the scope? >>> >>> BTW, the ":stepskip0" parameter does not seem to be included in >>> the manual. >> >> It is in the manual. >> >> - Carsten >>> >>> >>> Rainer >>> >>> >>> > > > Carsten, > > maybe I misunderstood. > > > 1. Without maxlevbel I get I get > > #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp > t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" > Clock summary at [2010-07-22 Do 09:07] > > | File | L | Timestamp | Headline | > Time | | | > |-------------------+---+---------------------+---------------- > +----------+--------+--------| > | | | Timestamp | *Total time* | > *327:51* | | | > ... > > > > with :maxlevel 0 I get > > > #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" > "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend > "<2010-07-31 Sa 23:55>" > Clock summary at [2010-07-22 Do 09:11] > > | File | L | Timestamp | Headline | Time | > |------+---+-----------+--------------+----------| > | | | Timestamp | *Total time* | *232:17* | > |------+---+-----------+--------------+----------| > #+END: > > > I would like to get the same results! > Is ":maxlevel 0" intended to not include the sublevel clocks? I think I have finally fixed this bug. Please verify. Bernt, I made a change to clock tables which I think I understand. But can you please watch out for inconsistencies with the newest version? Maybe run some tests with old and new version, to make sure clock tables deliver the same results? Thanks! - Carsten ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 11:30 ` Carsten Dominik @ 2010-10-26 13:53 ` Rainer Stengele 2010-10-26 14:27 ` Carsten Dominik 2010-10-26 15:52 ` Carsten Dominik 2010-10-30 16:18 ` Bernt Hansen 1 sibling, 2 replies; 12+ messages in thread From: Rainer Stengele @ 2010-10-26 13:53 UTC (permalink / raw) To: Carsten Dominik; +Cc: Bernt Hansen, org-mode List Am 26.10.2010 13:30, schrieb Carsten Dominik: > Hi Rainer, hi Bernt, > > On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > >> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>> >>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>> >>>> Hi all! >>>> >>>> lately I use the marvelous clocktables a lot... >>>> >>>> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >>>> >>>> The manual reads >>>> >>>> :maxlevel Maximum level depth to which times are listed in the table. >>>> >>>> which I misunderstood. >>>> I understood: an unlisted item does not mean that its time is not added! >>>> But it looks like ":maxlevel 0" does not add everything up. >>> >>> >>> I cannot reproduce this, :maxlevel 0 works for me. >>> >>>> >>>> Ok, maybe the manual is a bit misleading here. >>>> >>>> >>>> >>>> How can I get a clocktable without any details which simply adds up everything in the scope? >>>> >>>> BTW, the ":stepskip0" parameter does not seem to be included in the manual. >>> >>> It is in the manual. >>> >>> - Carsten >>>> >>>> >>>> Rainer >>>> >>>> >>>> >> >> >> Carsten, >> >> maybe I misunderstood. >> >> >> 1. Without maxlevbel I get I get >> >> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >> Clock summary at [2010-07-22 Do 09:07] >> >> | File | L | Timestamp | Headline | Time | | | >> |-------------------+---+---------------------+----------------+----------+--------+--------| >> | | | Timestamp | *Total time* | *327:51* | | | >> ... >> >> >> >> with :maxlevel 0 I get >> >> >> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >> Clock summary at [2010-07-22 Do 09:11] >> >> | File | L | Timestamp | Headline | Time | >> |------+---+-----------+--------------+----------| >> | | | Timestamp | *Total time* | *232:17* | >> |------+---+-----------+--------------+----------| >> #+END: >> >> >> I would like to get the same results! >> Is ":maxlevel 0" intended to not include the sublevel clocks? > > I think I have finally fixed this bug. Please verify. > > Bernt, I made a change to clock tables which I think I understand. But can you please watch out for inconsistencies with the newest version? Maybe run some tests with old and new version, to make sure clock tables deliver the same results? > > Thanks! > > - Carsten Hi Carsten, I checked and found: - clocktable sums are resulting in identical values, independant of the ":maxlevel" level - without ":maxlevel" parameter some tables now give slightly different results than in the past, some give identical results * I hope the new results are correct, but I did not have time to check in detail Looks good, I will test further. Thanks and thanks! -- Rainer ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 13:53 ` Rainer Stengele @ 2010-10-26 14:27 ` Carsten Dominik 2010-10-26 15:52 ` Carsten Dominik 1 sibling, 0 replies; 12+ messages in thread From: Carsten Dominik @ 2010-10-26 14:27 UTC (permalink / raw) To: Rainer Stengele; +Cc: Bernt Hansen, org-mode List On Oct 26, 2010, at 3:53 PM, Rainer Stengele wrote: > Am 26.10.2010 13:30, schrieb Carsten Dominik: >> Hi Rainer, hi Bernt, >> >> On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: >> >>> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>>> >>>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>>> >>>>> Hi all! >>>>> >>>>> lately I use the marvelous clocktables a lot... >>>>> >>>>> For toplevel clocktables which just sum up "all" I use >>>>> ":maxlevel 0" >>>>> >>>>> The manual reads >>>>> >>>>> :maxlevel Maximum level depth to which times are listed in >>>>> the table. >>>>> >>>>> which I misunderstood. >>>>> I understood: an unlisted item does not mean that its time is >>>>> not added! >>>>> But it looks like ":maxlevel 0" does not add everything up. >>>> >>>> >>>> I cannot reproduce this, :maxlevel 0 works for me. >>>> >>>>> >>>>> Ok, maybe the manual is a bit misleading here. >>>>> >>>>> >>>>> >>>>> How can I get a clocktable without any details which simply adds >>>>> up everything in the scope? >>>>> >>>>> BTW, the ":stepskip0" parameter does not seem to be included in >>>>> the manual. >>>> >>>> It is in the manual. >>>> >>>> - Carsten >>>>> >>>>> >>>>> Rainer >>>>> >>>>> >>>>> >>> >>> >>> Carsten, >>> >>> maybe I misunderstood. >>> >>> >>> 1. Without maxlevbel I get I get >>> >>> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp >>> t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >>> Clock summary at [2010-07-22 Do 09:07] >>> >>> | File | L | Timestamp | Headline >>> | Time | | | >>> |-------------------+---+---------------------+---------------- >>> +----------+--------+--------| >>> | | | Timestamp | *Total time* | >>> *327:51* | | | >>> ... >>> >>> >>> >>> with :maxlevel 0 I get >>> >>> >>> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" >>> "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend >>> "<2010-07-31 Sa 23:55>" >>> Clock summary at [2010-07-22 Do 09:11] >>> >>> | File | L | Timestamp | Headline | Time | >>> |------+---+-----------+--------------+----------| >>> | | | Timestamp | *Total time* | *232:17* | >>> |------+---+-----------+--------------+----------| >>> #+END: >>> >>> >>> I would like to get the same results! >>> Is ":maxlevel 0" intended to not include the sublevel clocks? >> >> I think I have finally fixed this bug. Please verify. >> >> Bernt, I made a change to clock tables which I think I understand. >> But can you please watch out for inconsistencies with the newest >> version? Maybe run some tests with old and new version, to make >> sure clock tables deliver the same results? >> >> Thanks! >> >> - Carsten > > Hi Carsten, > > I checked and found: > > - clocktable sums are resulting in identical values, independant of > the ":maxlevel" level > - without ":maxlevel" parameter some tables now give slightly > different results than in the past, some give identical results This is *very* bad. Please try to make me an example where it was different. - Carsten > * I hope the new results are correct, but I did not have time to > check in detail > > Looks good, I will test further. > > Thanks and thanks! > > -- Rainer > > - Carsten ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 13:53 ` Rainer Stengele 2010-10-26 14:27 ` Carsten Dominik @ 2010-10-26 15:52 ` Carsten Dominik 2010-10-26 22:55 ` Bernt Hansen 2010-10-27 7:01 ` Rainer Stengele 1 sibling, 2 replies; 12+ messages in thread From: Carsten Dominik @ 2010-10-26 15:52 UTC (permalink / raw) To: Rainer Stengele; +Cc: Bernt Hansen, org-mode List On Oct 26, 2010, at 3:53 PM, Rainer Stengele wrote: > Am 26.10.2010 13:30, schrieb Carsten Dominik: >> Hi Rainer, hi Bernt, >> >> On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: >> >>> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>>> >>>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>>> >>>>> Hi all! >>>>> >>>>> lately I use the marvelous clocktables a lot... >>>>> >>>>> For toplevel clocktables which just sum up "all" I use >>>>> ":maxlevel 0" >>>>> >>>>> The manual reads >>>>> >>>>> :maxlevel Maximum level depth to which times are listed in >>>>> the table. >>>>> >>>>> which I misunderstood. >>>>> I understood: an unlisted item does not mean that its time is >>>>> not added! >>>>> But it looks like ":maxlevel 0" does not add everything up. >>>> >>>> >>>> I cannot reproduce this, :maxlevel 0 works for me. >>>> >>>>> >>>>> Ok, maybe the manual is a bit misleading here. >>>>> >>>>> >>>>> >>>>> How can I get a clocktable without any details which simply adds >>>>> up everything in the scope? >>>>> >>>>> BTW, the ":stepskip0" parameter does not seem to be included in >>>>> the manual. >>>> >>>> It is in the manual. >>>> >>>> - Carsten >>>>> >>>>> >>>>> Rainer >>>>> >>>>> >>>>> >>> >>> >>> Carsten, >>> >>> maybe I misunderstood. >>> >>> >>> 1. Without maxlevbel I get I get >>> >>> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp >>> t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >>> Clock summary at [2010-07-22 Do 09:07] >>> >>> | File | L | Timestamp | Headline >>> | Time | | | >>> |-------------------+---+---------------------+---------------- >>> +----------+--------+--------| >>> | | | Timestamp | *Total time* | >>> *327:51* | | | >>> ... >>> >>> >>> >>> with :maxlevel 0 I get >>> >>> >>> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" >>> "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend >>> "<2010-07-31 Sa 23:55>" >>> Clock summary at [2010-07-22 Do 09:11] >>> >>> | File | L | Timestamp | Headline | Time | >>> |------+---+-----------+--------------+----------| >>> | | | Timestamp | *Total time* | *232:17* | >>> |------+---+-----------+--------------+----------| >>> #+END: >>> >>> >>> I would like to get the same results! >>> Is ":maxlevel 0" intended to not include the sublevel clocks? >> >> I think I have finally fixed this bug. Please verify. >> >> Bernt, I made a change to clock tables which I think I understand. >> But can you please watch out for inconsistencies with the newest >> version? Maybe run some tests with old and new version, to make >> sure clock tables deliver the same results? >> >> Thanks! >> >> - Carsten > > Hi Carsten, > > I checked and found: > > - clocktable sums are resulting in identical values, independant of > the ":maxlevel" level > - without ":maxlevel" parameter some tables now give slightly > different results than in the past, some give identical results > * I hope the new results are correct, but I did not have time to > check in detail > > Looks good, I will test further. no, this did not look good. I think I have found a bug, please pull again... - Carsten ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 15:52 ` Carsten Dominik @ 2010-10-26 22:55 ` Bernt Hansen 2010-10-27 7:01 ` Rainer Stengele 1 sibling, 0 replies; 12+ messages in thread From: Bernt Hansen @ 2010-10-26 22:55 UTC (permalink / raw) To: Carsten Dominik; +Cc: org-mode List, Rainer Stengele Carsten Dominik <carsten.dominik@gmail.com> writes: > On Oct 26, 2010, at 3:53 PM, Rainer Stengele wrote: > >> Am 26.10.2010 13:30, schrieb Carsten Dominik: >>> Hi Rainer, hi Bernt, >>> >>> On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: >>> >>>> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>>>> >>>>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>>>> >>>>>> Hi all! >>>>>> >>>>>> lately I use the marvelous clocktables a lot... >>>>>> >>>>>> For toplevel clocktables which just sum up "all" I use >>>>>> ":maxlevel 0" >>>>>> >>>>>> The manual reads >>>>>> >>>>>> :maxlevel Maximum level depth to which times are listed in >>>>>> the table. >>>>>> >>>>>> which I misunderstood. >>>>>> I understood: an unlisted item does not mean that its time is >>>>>> not added! >>>>>> But it looks like ":maxlevel 0" does not add everything up. >>>>> >>>>> >>>>> I cannot reproduce this, :maxlevel 0 works for me. >>>>> >>>>>> >>>>>> Ok, maybe the manual is a bit misleading here. >>>>>> >>>>>> >>>>>> >>>>>> How can I get a clocktable without any details which simply adds >>>>>> up everything in the scope? >>>>>> >>>>>> BTW, the ":stepskip0" parameter does not seem to be included in >>>>>> the manual. >>>>> >>>>> It is in the manual. >>>>> >>>>> - Carsten >>>>>> >>>>>> >>>>>> Rainer >>>>>> >>>>>> >>>>>> >>>> >>>> >>>> Carsten, >>>> >>>> maybe I misunderstood. >>>> >>>> >>>> 1. Without maxlevbel I get I get >>>> >>>> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp t >>>> :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >>>> Clock summary at [2010-07-22 Do 09:07] >>>> >>>> | File | L | Timestamp | Headline | >>>> Time | | | >>>> |-------------------+---+---------------------+---------------- >>>> +----------+--------+--------| >>>> | | | Timestamp | *Total time* | >>>> *327:51* | | | >>>> ... >>>> >>>> >>>> >>>> with :maxlevel 0 I get >>>> >>>> >>>> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") >>>> :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 >>>> Sa 23:55>" >>>> Clock summary at [2010-07-22 Do 09:11] >>>> >>>> | File | L | Timestamp | Headline | Time | >>>> |------+---+-----------+--------------+----------| >>>> | | | Timestamp | *Total time* | *232:17* | >>>> |------+---+-----------+--------------+----------| >>>> #+END: >>>> >>>> >>>> I would like to get the same results! >>>> Is ":maxlevel 0" intended to not include the sublevel clocks? >>> >>> I think I have finally fixed this bug. Please verify. >>> >>> Bernt, I made a change to clock tables which I think I understand. >>> But can you please watch out for inconsistencies with the newest >>> version? Maybe run some tests with old and new version, to make >>> sure clock tables deliver the same results? >>> >>> Thanks! >>> >>> - Carsten >> >> Hi Carsten, >> >> I checked and found: >> >> - clocktable sums are resulting in identical values, independant of >> the ":maxlevel" level >> - without ":maxlevel" parameter some tables now give slightly >> different results than in the past, some give identical results >> * I hope the new results are correct, but I did not have time to >> check in detail >> >> Looks good, I will test further. > > no, this did not look good. > > I think I have found a bug, please pull again... > > - Carsten Hi Carsten, I haven't had time to pull the new clock table code yet. I'll try to get to it by the end of the week. I don't currently use clock tables all that much other than R in the agenda. Thanks for testing this early Rainer. Regards, Bernt ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 15:52 ` Carsten Dominik 2010-10-26 22:55 ` Bernt Hansen @ 2010-10-27 7:01 ` Rainer Stengele 1 sibling, 0 replies; 12+ messages in thread From: Rainer Stengele @ 2010-10-27 7:01 UTC (permalink / raw) Cc: Bernt Hansen, org-mode List Am 26.10.2010 17:52, schrieb Carsten Dominik: > > On Oct 26, 2010, at 3:53 PM, Rainer Stengele wrote: > >> Am 26.10.2010 13:30, schrieb Carsten Dominik: >>> Hi Rainer, hi Bernt, >>> >>> On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: >>> >>>> Am 21.07.2010 16:24, schrieb Carsten Dominik: >>>>> >>>>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote: >>>>> >>>>>> Hi all! >>>>>> >>>>>> lately I use the marvelous clocktables a lot... >>>>>> >>>>>> For toplevel clocktables which just sum up "all" I use ":maxlevel 0" >>>>>> >>>>>> The manual reads >>>>>> >>>>>> :maxlevel Maximum level depth to which times are listed in the table. >>>>>> >>>>>> which I misunderstood. >>>>>> I understood: an unlisted item does not mean that its time is not added! >>>>>> But it looks like ":maxlevel 0" does not add everything up. >>>>> >>>>> >>>>> I cannot reproduce this, :maxlevel 0 works for me. >>>>> >>>>>> >>>>>> Ok, maybe the manual is a bit misleading here. >>>>>> >>>>>> >>>>>> >>>>>> How can I get a clocktable without any details which simply adds up everything in the scope? >>>>>> >>>>>> BTW, the ":stepskip0" parameter does not seem to be included in the manual. >>>>> >>>>> It is in the manual. >>>>> >>>>> - Carsten >>>>>> >>>>>> >>>>>> Rainer >>>>>> >>>>>> >>>>>> >>>> >>>> >>>> Carsten, >>>> >>>> maybe I misunderstood. >>>> >>>> >>>> 1. Without maxlevbel I get I get >>>> >>>> #+BEGIN: clocktable :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >>>> Clock summary at [2010-07-22 Do 09:07] >>>> >>>> | File | L | Timestamp | Headline | Time | | | >>>> |-------------------+---+---------------------+----------------+----------+--------+--------| >>>> | | | Timestamp | *Total time* | *327:51* | | | >>>> ... >>>> >>>> >>>> >>>> with :maxlevel 0 I get >>>> >>>> >>>> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa 23:55>" >>>> Clock summary at [2010-07-22 Do 09:11] >>>> >>>> | File | L | Timestamp | Headline | Time | >>>> |------+---+-----------+--------------+----------| >>>> | | | Timestamp | *Total time* | *232:17* | >>>> |------+---+-----------+--------------+----------| >>>> #+END: >>>> >>>> >>>> I would like to get the same results! >>>> Is ":maxlevel 0" intended to not include the sublevel clocks? >>> >>> I think I have finally fixed this bug. Please verify. >>> >>> Bernt, I made a change to clock tables which I think I understand. But can you please watch out for inconsistencies with the newest version? Maybe run some tests with old and new version, to make sure clock tables deliver the same >>> results? >>> >>> Thanks! >>> >>> - Carsten >> >> Hi Carsten, >> >> I checked and found: >> >> - clocktable sums are resulting in identical values, independant of the ":maxlevel" level >> - without ":maxlevel" parameter some tables now give slightly different results than in the past, some give identical results >> * I hope the new results are correct, but I did not have time to check in detail >> >> Looks good, I will test further. > > no, this did not look good. > > I think I have found a bug, please pull again... > > - Carsten > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > Hi Carsten, same behaviour as before. Below are the two clocktables, one from August, 2nd, version unknown, probably development version from that day or before, the first one from today. The result of the current version is always the same, independant of the :maxlevel level I have deleted the Headlines. #+BEGIN: clocktable :scope ("~/org/DIPLAN/FILE2.org" "~/org/DIPLAN/FILE1/FILE1.org" "~/org/DIPLAN/FILE1/Lastenheft.org" "~/org/DIPLAN/FILE1/Pflichtenheft.org") :block 2010-05 Clock summary at [2010-10-27 Mi 08:50], for Mai 2010. | File | L | Headline | Time | | | |-------------------+---+--------------+---------+-------+-------| | | | *Total time* | *86:31* | | | |-------------------+---+--------------+---------+-------+-------| | FILE1.org | | *File time* | *78:22* | | | | FILE1.org | 1 | | 78:22 | | | | FILE1.org | 2 | | | 45:41 | | | FILE1.org | 3 | | | | 45:41 | | FILE1.org | 2 | | | 3:23 | | | FILE1.org | 3 | | | | 0:14 | | FILE1.org | 3 | | | | 2:14 | | FILE1.org | 3 | | | | 0:20 | | FILE1.org | 3 | | | | 0:35 | | FILE1.org | 2 | | | 5:18 | | | FILE1.org | 3 | | | | 3:18 | | FILE1.org | 3 | | | | 2:00 | | FILE1.org | 2 | | | 24:00 | | | FILE1.org | 3 | | | | 5:02 | | FILE1.org | 3 | | | | 8:10 | | FILE1.org | 3 | | | | 1:30 | | FILE1.org | 3 | | | | 9:18 | |-------------------+---+--------------+---------+-------+-------| | Lastenheft.org | | *File time* | *6:04* | | | | Lastenheft.org | 1 | | 6:04 | | | | Lastenheft.org | 2 | | | 6:04 | | | Lastenheft.org | 3 | | | | 4:15 | |-------------------+---+--------------+---------+-------+-------| | Pflichtenheft.org | | *File time* | *2:05* | | | | Pflichtenheft.org | 1 | | 2:05 | | | | Pflichtenheft.org | 2 | | | 2:05 | | | Pflichtenheft.org | 3 | | | | 2:05 | #+END: #+BEGIN: clocktable :scope ("~/org/DIPLAN/FILE2.org" "~/org/DIPLAN/FILE1/FILE1.org" "~/org/DIPLAN/FILE1/Lastenheft.org" "~/org/DIPLAN/FILE1/Pflichtenheft.org") :block 2010-05 Clock summary at [2010-08-02 Mo 08:48], for Mai 2010. | File | L | Headline | Time | | | |-------------------+---+--------------+---------+-------+-------| | | | *Total time* | *74:35* | | | |-------------------+---+--------------+---------+-------+-------| | FILE1.org | | *File time* | *55:16* | | | | FILE1.org | 1 | | 55:16 | | | | FILE1.org | 2 | | | 35:31 | | | FILE1.org | 3 | | | | 35:31 | | FILE1.org | 2 | | | 3:23 | | | FILE1.org | 3 | | | | 0:14 | | FILE1.org | 3 | | | | 2:14 | | FILE1.org | 3 | | | | 0:20 | | FILE1.org | 3 | | | | 0:35 | | FILE1.org | 2 | | | 5:18 | | | FILE1.org | 3 | | | | 3:18 | | FILE1.org | 3 | | | | 2:00 | | FILE1.org | 2 | | | 11:04 | | | FILE1.org | 3 | | | | 5:02 | | FILE1.org | 3 | | | | 1:55 | | FILE1.org | 3 | | | | 1:30 | | FILE1.org | 3 | | | | 2:37 | |-------------------+---+--------------+---------+-------+-------| | Lastenheft.org | | *File time* | *17:14* | | | | Lastenheft.org | 1 | | 17:14 | | | | Lastenheft.org | 2 | | | 6:04 | | | Lastenheft.org | 3 | | | | 4:15 | | Lastenheft.org | 2 | | | 11:10 | | | Lastenheft.org | 3 | | | | 3:04 | |-------------------+---+--------------+---------+-------+-------| | Pflichtenheft.org | | *File time* | *2:05* | | | | Pflichtenheft.org | 1 | | 2:05 | | | | Pflichtenheft.org | 2 | | | 2:05 | | | Pflichtenheft.org | 3 | | | | 2:05 | #+END: Does that help you? Probably not. I do not know if I am able to create an example. Maybe I could send you one of the files with differing results privately? Best -- Rainer ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items 2010-10-26 11:30 ` Carsten Dominik 2010-10-26 13:53 ` Rainer Stengele @ 2010-10-30 16:18 ` Bernt Hansen 1 sibling, 0 replies; 12+ messages in thread From: Bernt Hansen @ 2010-10-30 16:18 UTC (permalink / raw) To: Carsten Dominik; +Cc: org-mode List, Rainer Stengele Carsten Dominik <carsten.dominik@gmail.com> writes: > Hi Rainer, hi Bernt, > > On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > >> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") >> :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa >> 23:55>" >> Clock summary at [2010-07-22 Do 09:11] >> >> | File | L | Timestamp | Headline | Time | >> |------+---+-----------+--------------+----------| >> | | | Timestamp | *Total time* | *232:17* | >> |------+---+-----------+--------------+----------| >> #+END: >> >> >> I would like to get the same results! >> Is ":maxlevel 0" intended to not include the sublevel clocks? > > I think I have finally fixed this bug. Please verify. > > Bernt, I made a change to clock tables which I think I understand. > But can you please watch out for inconsistencies with the newest > version? Maybe run some tests with old and new version, to make sure > clock tables deliver the same results? > > Thanks! > > - Carsten Hi Carsten, I've been at a commit before the clock tables change until today. I've update to the current master and reviewed my agenda clock table results for every day in October and the results are identical for me before and after this change. Thanks, Bernt ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2010-10-30 16:18 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-07-13 9:21 clocktable: maximum level 0 does not only avoid listing items but also does not calculate items Rainer Stengele 2010-07-21 14:24 ` Carsten Dominik 2010-07-22 7:16 ` Rainer Stengele 2010-07-22 7:47 ` Carsten Dominik 2010-10-07 8:41 ` Rainer Stengele 2010-10-26 11:30 ` Carsten Dominik 2010-10-26 13:53 ` Rainer Stengele 2010-10-26 14:27 ` Carsten Dominik 2010-10-26 15:52 ` Carsten Dominik 2010-10-26 22:55 ` Bernt Hansen 2010-10-27 7:01 ` Rainer Stengele 2010-10-30 16:18 ` Bernt Hansen
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).