Page History

Development

1. PingER Data Explorer Explorer - Joao
   1. Partially working version is here
   2. Need to add 2014, 2015.
   3. Fix up PingER Motion metrics, if Data Explorer works we do not need this.
      1. documentation
      for Amber's version where the data is at Google
      1. is here, 
      2. There is a partially working version that needs files updating here
2. Fix up Google map of PingER sites. - Joao
   1. Partially working version is here. Need to add 2014, 2015.
   2. Further extension of the PingER coverage map front end.  For example updating to work properly on MSIE and Firefox.
3. PingER Metrics intensity maps - Joao
   1. See here 
4. Coordinate and lead the installation of PingER monitoring at multiple Malaysian sites -  Saqib
5. Deploy an ePingER at Bario in the Highlands. Also look at deploying a network of PingER monitoring sites in Malaysia.
6. Managing <HostList> for Malaysia from Johari. Since the number of monitoring nodes in Malaysia is likely to grow, I think it is a good idea to start thinking of automated ways of synchronizing the <HostList> section. A few thoughts on this matter:
   1. we can use the same approach as the automatic updating/sync of the Beacon List. This would require modifications to pinger2.pl
   2. which node will be the trusted/root node in Malaysia for updating? since any single monitoring host can add any number of new hosts, might a mechanism to cross check between monitoring hosts.
7. Extend the NODEDETAILS data base to allow entry more carefully validate input.
8. Improve the PingER2 installation procedures to make it more robust. This might be something for the person(s) in Pakistan or UNIMAS who are responsible for installing PingER2 at the Pakistani or Malaysian monitoring sites. Look at the FAQ, and ping_data.pl which has been improved to assist in debugging, could it be further improved. - Johari
   1. Build a new makefile (see http://www-iepm.slac.stanford.edu/pinger/tools/pingER-2.0.2.tar.gz) with the latest pinger2.pl and other fixes.
9. Migrate PingER to IPv6. Fix PingER archiving/analysis package to be IPv6 conformant. With Malaysia moving quickly to IPv6 (already Nava at USM has sent Les an IPv6 address that he recommends monitoring), converting PingER (especially the gathering, analysis) work with IPv6 is an interesting problem.  See Make PingER IPv6 compliant for some thoughts on getting started. Anjum believes he could provide an undergraduate to start on this, and Adib at UUM is interested.
10. With PingER going back over a decade, its presentation tools tend to be a bit jaded having in some cases been developed in the 90's. New, modern ways to access display and navigate the data would be a big plus. Bebo proposes two projects below. If these are of interest, Bebo is willing to work with students who come to SLAC and remotely with students at UNIMAS and NUST. Bebo believes that both of these areas have great potential for papers within the conference communities with which he is directly involved.
    1. Creative visualization of PingER data including rich interaction;
    2. Publication of PingER data in Linked Open Data formats thereby increasing its usefulness to other researchers. An example is RDF/XML. This could be a development project (as opposed to research) for a final year student. Anjum pointed out that converting the PingER storage mechanism is a major task based on the experience at NUST when they converted te SLAC PingER flat files to a database. On the other hand maybe one coud could do the conversion on the fly in response to a request. Johari might be able to use some of the funding he received for such a development project (e.g. to enhance pingtable.pl to add this format to its download capabilities). This is being tackled by Renan Souza of UFRJ but not completed.
11. Network constellation maps.Further extension of the PingER coverage map front end.  For example updating to work properly on MSIE and Firefox.
12. Using Microsoft Geoflow or Google /maps/earth, create a visualization identifying PingER monitored hosts with the size of the dot representing one metric, the color of the dot another metric, and the blink rate the losses. Selection of the monitoring host, metric 1, metric 2, relation between dot size/blink rate and metric value etc. Should be playable in time so selection of time steps.
13. Event detection using RRDs and Holt-Winters.
14. Alerting mechanisms
15. PingER Big data Analytics MD NOR RIDZUAN BIN DAUD <ridzuan@um.edu.my>
16. Distributed Ping Project (DPP), also the DPP web home page
17. Port PingER to Google
18. Mobility and PingER
19. Unify data storage for PingER Raw data

...