...
Ibrahim Abaker is planning to work on topic initially entitled " leveraging pingER big data with a modified pingtable for event-correlation and clustering", The purpose of this project is to make Pinger more efficient and more scalable to retrieve and analysis pingER raw data. consequently Consequently it may improve pinger data store. He is planning to use key-value store model with high expandability and shorter query response time. The benefit of such project will help in the design of real time analysis and distributed pinger data across multiple servers for analysis. Les has sent him a pointer to documentation on the data flow at SLAC and also listings of pingtable.pl and associated script. He is currently writing a proposal, which will contain a problem statement, objectives, scope and the approach to tackle the problem. He asked: how much PingER data is captured and stored so far (~ 1TByte)? Is there a published paper (see http://www-iepm.slac.stanford.edu/paperwork/ieee/ieee.pdf)?
UNIMAS
The Raspberry Pi is at the data centre, but due to miscommunication, the public ip which was previously assigned to the rasp pi unit has been assigned to another server. So now Johari has to wait for the ip to be reassigned back to rasp pi unit and give new ip to the other server. They suggested a new ip for the rasp pi unit but Johari wanted to have the old one so that we do not have to update the record at slac for the archival process, etc
...