This is mainly a list of tasks for Amber. They will provide:

• improved PingER management,
• better quality of PingER data,
• improved understanding of PingER for Amber
• and an opportunity for Amber to learn coding techniques by reviewing the code of others.

Make sure Amber reads the document on writing and debugging perl scripts. Update it as learn more.

Update beacons

• Find non-responding Beacons and replace as needed.  - DONE 4/29/2011-

Bad IP addresses

• Learn how to use Down sites
  • Why does guthrie-names.pl report an error for pinger.slac.stanford.edu
• Using downsites.cgi clean up incorrect IP addresses: DONE 5/10/2011
  • using clusters
  • fixing up NODEDETAILS

Guthrie NODEDETAILS database

Improve validation of data entry focusing on common errors, e.g.

• Verify lat long is two decimal numbers with a space between them
• Validate the IP address (IPv6 or IPv4)
• Verify the hostname, sitename

Clean up bad min_RTTs

• using prm.pl with Alpha metric, identify Alphas > 2, and use filter to remove bad data. -- DONE 4/29/2011
• Use motion metrics and normalized throughput to ID bad RTTs etc. - DONE 5/3/2011

Verify Alpha and MOS analyses

• prm.pl, extend to ID bad MOS
• pingtable.pl
• Should prm.pl work with Pakistan if not fix

Extend motion metrics

• Add MOS and possibly Alpha
• Plot Excel bubble plot of  Network Readiness Index from http://reports.weforum.org/global-information-technology-report/ against throughput.

Identify monitors down for n days

• If monitor not Penalized identify if down and mark as penalized
• If penalized and is working then removed Penalized marker
• using penalized marker do not issue warnings from checkdata if Penalized
• Provide a web page showing penalized state

Decide on project

• look at project list