[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-30 Thread Bernt Hansen
Carsten Dominik carsten.domi...@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

___
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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-27 Thread Rainer Stengele
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

 :maxlevelMaximum 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 |  

[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-26 Thread 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

:maxlevelMaximum 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

___
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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-26 Thread Rainer Stengele
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

 :maxlevelMaximum 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



___
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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-26 Thread 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

:maxlevelMaximum 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




___
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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-26 Thread 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

:maxlevelMaximum 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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-10-07 Thread Rainer Stengele
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

 :maxlevelMaximum 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


___
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


[Orgmode] Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

2010-07-22 Thread Rainer Stengele
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

 :maxlevelMaximum 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

___
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