Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

 

Time & date 

Wednesday Dec 7th  8:00pm Pacific Standard Time, Thursday Dec 7th 9:00am Pakistan time, Thursday Dec 27th  2016 12:00noon Malaysian time, 

...

PingER for Android (see ePingER on Android two methods).

Amity - Java approach (A. Sai Sabitha and Shivnarayan Rajappa)
  1. They are using the native java tools, they are not running the pinger2.pl <http://pinger2.pl>  script on android since the native java tools have the following advantages
    1. easier for user, 
    2. no need for prior installation of any software, e.g. load perl interpreter which may require missing skills, especially for a non technical user
    3. doesn't need a rooted phone
    4. only the apk needs to be installed to run
  2.  They have fixed the final sequence number change by using regex, and  pushed these changes to github repository.

  3. They have installed apache tomcat in the server and plan to use a java file on the server which would connect to the phones that send the request. This java file will then take the input stream received from the phone and write the output stream to a file that would be stored on the server. We are facing some problems regarding a blocked port that is not allowing the phone to connect to the server we are currently working on resolving the issue.

  4.  SLAC can then regularly pull these files which would be stored based on the month they are received. 

  5. The Android students have started writing a paper on " implementation  of pinger  on android " .

  6. Next steps:

    1. Extend the target list by getting the Beacon list from SLAC. It is at http://www-iepm.slac.stanford.edu/pinger/pinger.xml on a regular basis and updating the <BeaconList> section at their site. This was part of pinger2.pl

    2. Also they will need a utility to clean out old recorded data (say older than 3 months), since it will be gathered from SLAC (via the proxy) and eventually they may run out memory on the Android.
Discussion

To a large extent it depend on how we plan to use this.

  • If the phones are just MAs in a fixed location then simply porting pinger2.pl is easier and probably sufficient.  
  • If this is intended to grow into a mobile application for general use then it needs to be the Java implementation.

A next step is to get the data from the phone MA to the archive at SLAC. The current method ping_data.pl requires a public IP address for the phone which may not exist if its is mobile. Getting the MA to put the data to the archive may raise some security issue for the archiver.

Amity 

Tropical cyclone Vardah hit Chennai in India on the Dec 13th. It impacted the Internet, in particular one of Airtel's undersea cables. Les sent email to A. Sai Sabitha to see if  PingER from Amity could see any effect.

Saqib also reported that there was also a cable cut between Singapore and Europe on October 4, 2016 in SEA-ME-WE 4. Thus affecting the internet speed in south Asia and south-east Asia.

UUM

From Adib:

  • Adib has written a very nice paper on a case study of ASEAN countries Internet connectivity seen from SLAC and relating that to various socio-economic indices. Is there an update 12/4/2016

  • We are working with SLAC the DoE etc. to get an invite to Adib to visit SLAC.

  • Adib asked a student (Jaafrau)  to explore  “Creative visualization of PingER data, including rich interaction;”.  He has come up with a good design, yet the development part needs a lot of work. Adib will ask him to upload his interface and share the link. No update 8/24/2016 is there an update?

  • Adib has another student starting in September. Adib will look at directing him to PingER.  Any update?

  • Adib had a meeting with Mr. Chaisit Choosong <chaisitc@gmail.com>, from Rajamangala University of Technology Srivijaya last week. Adib  gave him a brief about PingER project, aim, objectives, and its installation requirements.  He is interested to setup a PingER monitoring node at his site. Adib sent another email to introduce Chaisit to Dr. Les and hopefully, Les has followed up with an email on 8/21/2016 with an invitation and information on how to set up the monitor. Adib  will follow  up.  We at SLAC have not heard anything 10/26/2016, Sent an email 12/4/2016, 12/7/2016.

UNIMAS No update from Johari

pinger.unimas.my was not pingable. Fixed.

...

Johari looking at a PingER workshop May 17th 2017 at Unimas.

UAF (Saqib) No update from Saqib  12/14/2016

MA Device at UAF ready, will assign live IP to machine next week, then will contact Les to try and gather data.

...

Next Meeting

Next meeting:  Wednesday Jna Jan 11th 8pm Pacific time,  Thursday Jan 12th, 2016  9:00am Pakistan time, Thursday Jan 12th 2016 12:00noon Malaysian time


Old information

Amity - Java approach (A. Sai Sabitha and Shivnarayan Rajappa)
  1. They are using the native java tools, they are not running the pinger2.pl <http://pinger2.pl>  script on android since the native java tools have the following advantages
    1. easier for user, 
    2. no need for prior installation of any software, e.g. load perl interpreter which may require missing skills, especially for a non technical user
    3. doesn't need a rooted phone
    4. only the apk needs to be installed to run
  2.  They have fixed the final sequence number change by using regex, and  pushed these changes to github repository.

  3. They have installed apache tomcat in the server and plan to use a java file on the server which would connect to the phones that send the request. This java file will then take the input stream received from the phone and write the output stream to a file that would be stored on the server. We are facing some problems regarding a blocked port that is not allowing the phone to connect to the server we are currently working on resolving the issue.

  4.  SLAC can then regularly pull these files which would be stored based on the month they are received. 

  5. The Android students have started writing a paper on " implementation  of pinger  on android " .

  6. Next steps:

    1. Extend the target list by getting the Beacon list from SLAC. It is at http://www-iepm.slac.stanford.edu/pinger/pinger.xml on a regular basis and updating the <BeaconList> section at their site. This was part of pinger2.pl

    2. Also they will need a utility to clean out old recorded data (say older than 3 months), since it will be gathered from SLAC (via the proxy) and eventually they may run out memory on the Android.
Discussion

To a large extent it depend on how we plan to use this.

  • If the phones are just MAs in a fixed location then simply porting pinger2.pl is easier and probably sufficient.  
  • If this is intended to grow into a mobile application for general use then it needs to be the Java implementation.

A next step is to get the data from the phone MA to the archive at SLAC. The current method ping_data.pl requires a public IP address for the phone which may not exist if its is mobile. Getting the MA to put the data to the archive may raise some security issue for the archiver.

...