13 |
|
<center><h3>Current Status</h3></center> |
14 |
|
|
15 |
|
<p align="justify"> |
16 |
< |
<img src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="left"> |
16 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a> |
17 |
|
All i-scream components now function to initial |
18 |
|
design parameters and our system is regarded to be complete. |
19 |
|
<b><a href="worddocs/">Documentation</a></b> is available to assist third party programmers |
23 |
|
</p> |
24 |
|
|
25 |
|
<p align="justify"> |
26 |
< |
<img src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="right"> |
26 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a> |
27 |
> |
|
28 |
|
The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a> |
29 |
|
are now visible on the web. If you are <b>not</b> a local user, then you may |
30 |
|
view some of the output in the <b><a href="screenshots/">screenshots</a></b> section. |
36 |
|
</p> |
37 |
|
|
38 |
|
<p align="justify"> |
39 |
< |
<img src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"> |
39 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a> |
40 |
|
Our current host development allows us to pass machine statistics |
41 |
|
to our distributed filter arrangement, which then processes the |
42 |
|
data and stores it for later use. An example of such use is the |
47 |
|
</p> |
48 |
|
|
49 |
|
<p align="justify"> |
50 |
< |
<img src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"> |
50 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a> |
51 |
|
The latest builds of the i-scream Distributed Central Monitoring System |
52 |
|
are now available for <b><a href="/downloads/">download</a></b> from this |
53 |
|
website. To assist in our addition of features to the system, we |
60 |
|
<center><h3>Project Completion</h3></center> |
61 |
|
|
62 |
|
<p align="justify"> |
63 |
< |
<img src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"> |
63 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a> |
64 |
|
The i-scream Distributed Central Monitoring System started off as |
65 |
|
a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at |
66 |
|
the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK. |
69 |
|
lever arch folders. The project, consisting of source code, user, |
70 |
|
maintenance and other documents, was handed in at 3pm. The CVS |
71 |
|
repository was tagged to signify the project's completion, however, |
72 |
< |
the project is still being developed by the <a href="acknowledgments.shtml">core development team</a> |
72 |
> |
the project is still being developed by the <a href="acknowledgements.shtml">core development team</a> |
73 |
|
as we have found the system to be very useful in practice. We would |
74 |
|
love to hear of ideas for extra features that we may include in the |
75 |
|
next builds. |
76 |
|
</p> |
77 |
|
|
78 |
|
<p align="justify"> |
79 |
< |
<img src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"> |
80 |
< |
As can be seen in our "<a href="worddocs/">problem domain</a>" document, the project |
79 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a> |
80 |
> |
As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project |
81 |
|
was aimed at the UKC Computer Science department, and as such |
82 |
|
we believed that a demonstration to the "customer" was important. The |
83 |
|
feedback from our demonstation was more positive than we had |
90 |
|
<center><h3>Naming History</h3></center> |
91 |
|
|
92 |
|
<p align="justify"> |
93 |
< |
<img src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"> |
93 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a> |
94 |
|
The name <i>i-scream</i> arose from a meeting whereupon one member |
95 |
|
of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board. |
96 |
|
It later became apparent that we had no name for our project (other |