Re: historystats file format documentation

Zdeněk Kedaj <[email protected]> writes:

> Hello everyone, 
> is there any documentation on the historystats file? I want to know the meaning
> of the rows and numbers in this file as I am going to write Java app for
> extract the data to some format that can be easily read/imported to some
> statistics software. Although I can guess the format I would like some more
> feedback from people who really know the meaning of those numbers.

Here is a relevant comment from contrib/plot/workrave-dump in the
Workrave 1.8.5 distribution:

# WorkRaveStats 4
# D 16 5 104 14 51 17 5 104 3 59
# B 0 7 9 8 40 0 0 9 386 
# B 1 7 4 1 0 1 3 4 362 
# B 2 7 0 0 0 0 0 0 0 
# m 6 6049 234742 113560 266 417 16617 
# D 17 5 104 16 49 18 5 104 3 59
# B 0 7 1 0 3 0 0 1 526 
# B 1 7 3 0 0 0 2 2 1768 
# B 2 7 0 0 0 0 0 0 872 
# m 6 15272 39275 11937 36 30 1899 
#
# D(ate):	[ tm_mday tm_mon tm_year tm_hour tm_min ] {2}
#
# B(reak):	<t> <nn> <x0> <x1> <x2> <x3> <x4> <x5> <x6>
#
#	<t> = break type
# 		0 = microbreak
#		1 = rest break
#		2 = daily limit
#
#	<nn> STATS_BREAKVALUE_SIZEOF - number of following numbers
#
#	<x0> STATS_BREAKVALUE_PROMPTED - break prompts<x6> + repeated prompts
#	<x1> STATS_BREAKVALUE_TAKEN - prompted breaks taken
#	<x2> STATS_BREAKVALUE_NATURAL_TAKEN - natural breaks taken
#	<x3> STATS_BREAKVALUE_SKIPPED - breaks skipped
#	<x4> STATS_BREAKVALUE_POSTPONED - breaks postponed
#	<x5> STATS_BREAKVALUE_UNIQUE_BREAKS - break prompts
#	<x6> STATS_BREAKVALUE_TOTAL_OVERDUE - overdue time (seconds)
#
# m(isc):	<nn> <x0> <x1> <x2> <x3> <x4> <x5>
#
# 	<nn> STATS_VALUE_SIZEOF
#	<x0> STATS_VALUE_TOTAL_ACTIVE_TIME (seconds)
#	<x1> STATS_VALUE_TOTAL_MOUSE_MOVEMENT
#	<x2> STATS_VALUE_TOTAL_CLICK_MOVEMENT
#	<x3> STATS_VALUE_TOTAL_MOVEMENT_TIME (seconds)
#	<x4> STATS_VALUE_TOTAL_CLICKS
#	<x5> STATS_VALUE_TOTAL_KEYSTROKES

I hope this helps.

-- 
With my best regards,

Joe Wells


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Workrave-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/workrave-user