YIKES!!! You don't want much, eh??? This was always planned,
but real life seems to always come and whack me around the
head every time I get up the motivation to implement. Lets
see what I can do for 2.2.0...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since the Seti stats server is not always available
(well I don't know for you but I haven't been able to
chack my stats for months), some stats stored locally
might be nice and useful and it wouldn't take too much
space on Hard disk. So I see things like:
Unit number/start date/end date/calculation time/total
cpu time after calculation/best spike/best gaussian
140 12/24/2000 12/25/2000 10:25:32 282
days xxx xxx
141 12/26/2000 12/28/2000 10:15:22 282
days xxx xxx
142 12/29/2000 12/30/2000 10:21:45 283
days xxx xxx
All that stored in a text file viewable through an
option calling the Gnome viewer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=20532
YIKES!!! You don't want much, eh??? This was always planned,
but real life seems to always come and whack me around the
head every time I get up the motivation to implement. Lets
see what I can do for 2.2.0...
Logged In: YES
user_id=20532
[Extracted from support request 307973]
Since the Seti stats server is not always available
(well I don't know for you but I haven't been able to
chack my stats for months), some stats stored locally
might be nice and useful and it wouldn't take too much
space on Hard disk. So I see things like:
Unit number/start date/end date/calculation time/total
cpu time after calculation/best spike/best gaussian
140 12/24/2000 12/25/2000 10:25:32 282
days xxx xxx
141 12/26/2000 12/28/2000 10:15:22 282
days xxx xxx
142 12/29/2000 12/30/2000 10:21:45 283
days xxx xxx
All that stored in a text file viewable through an
option calling the Gnome viewer.