 |
Ksetiwatch |
What's this?
News
Screenshots
Download
Discussion Forum
Project Page
Online Docs
This project is hosted by
|
Ksetiwatch is a monitoring tool for the
Seti@home
distributed computing project, which searches for signals of extraterrestrial
life. It displays the state of the Seti@home client(s) running on your
computer or in your local network, and logs/manages completed work units.
News
|
Apr-28-2000
|
You want to see your top Gaussians as a graph? Then version 0.5.0 is something
for you. Of course, this feature requires SETI@home clients with version number
2.0 or higher (older clients are still supported, but it will not be possible
to display the graphs). The complete list of changes:
-
Gaussian graphs. To display a Gaussian, right-click on the respective location
in the `Analysis' tab and choose "Show Gaussian...". The graph is shown in a
separate window, which you can arbitrarily resize. For those of you who like to
play around a bit, I have added some options affecting the graph's appearance.
Just right-click on the Gaussian graph for a pop-up menu.
-
The csvdatabase class has been completely rewritten. Displaying the lists of
logged WUs is really fast now.
-
Newer S@h clients don't update so often any more. Increased an internal
timeout value to 90 s in order to prevent the status display from constantly
switching between running and stopped.
|
|
Apr-22-2000
|
|
Finally, I've got Gaussian graphs up and running. Here is a screenshot
of the widget:

Of course, it needs a little more tweaking, but expect a new version soon.
This page has grown a little too big. I decided to move older news to a
separate page. See below for a link.
|
|
Apr-14-2000
|
Another bugfix release is out. The following changes have been made in
version 0.4.3:
-
Logging of completed work units can be switched off for selected locations.
Have a look at the dialog window (of course, it is enabled by default).
-
Ksetiwatch now remembers not only its size, but also its position after
a restart. Note: after upgrading to 0.4.3, the window size will be
reset to the default value. Just resize the window again, place it at
your preferred screen position and you're done.
-
The process id is now taken from the `pid.sah' file to stop the S@h client.
This is to ensure that this function works on all Unix systems (I hope).
-
I decided to stop the experiment with redirecting the client's output to
/dev/null, since newer clients aren't so verbose any more.
-
The `About' widget didn't resize properly; fixed (thanks to Peter Drumm
for pointing this out).
-
Clicking on the header of the summary list in the `Completed WU' tab has
no effect any more. `Grand Total' will now always be the last entry in the
list.
-
User name and version info weren't correctly added to the log file when
logging a WU; fixed (thanks to Hans Motshärg for several log-file-related
hints).
This is probably the last release which supports the old 1.x clients. I
guess you all have upgraded by now. The next version will include a
graphical view of the top Gaussian of every work unit, so stay tuned.
|
|
Mar-27-2000
|
Just thought I keep you busy with updating. Version 0.4.2 includes the following
changes:
-
The summary list in the `Completed WU' tab now counts only logged WUs.
-
Increased an internal timeout value to prevent the status display from
toggling between running and stopped when monitoring newer clients.
-
Locations could appear below the `Grand Total' entry in the `Completed WU'
tab; fixed (but don't click on the header :-/ ).
-
Redirecting the standard error output ("2>") to /dev/null may produce an
error with shells other than bash; disabled for the time being.
-
Monitoring process was blocked when a message box reporting a high signal
popped up. Made all message boxes modeless now.
-
Ksetiwatch now looks into the logged WU lists for record scores and
updates its record entries accordingly.
I have closed all NFS-related bugs on the bug list on the project page. If
you still have problems please resubmit.
|
|
Mar-17-2000
|
| Apart from redecorating my new home,
I spent much time in the last weeks to find a solution for the
networking problems reported by several users. Somehow Ksetiwatch seems to
trigger a bug in the NFS-related part of the Linux kernel. A kind user
came up with a workaround, which obviously does the trick (thanks, Frode!).
This workaround is included in the new release. The complete changelog
for version 0.4.1 looks like this:
New feature:
-
Enabled sorting in all list views. Locations and work units can be sorted
in ascending or descending order, e.g. with respect to processing time or
strongest Gaussian.
Bugfixes:
-
Applied a workaround to prevent hangs when monitoring clients in NFS-mounted
directories.
-
Logging of WUs now gives a more descriptive error message in case of a
failure.
-
Empty locations (without a WU) occasionally appeared on the skymap at (0 hr, 0 deg);
fixed.
-
Starting the SETI@home client via Ksetiwatch now invokes a KShellProcess;
text output is dumped to /dev/null by default.
-
Various other minor improvements.
|
|
Mar-15-2000
|
I have found a nice page dealing with SETI@home under Linux, and
describing in particular the problems when running clients in NFS mounted directories.
If you're interested, click here.
|
|
Mar-02-2000
|
Updated the screenshot page to keep it in sync with the recent
development on Ksetiwatch.
|
|