Time
The proposed date is January 2nd, 7:00-7:45 pm San Francisco time (this is 8:30 am - 9:15 am January 3rd India Standard Time).
Invitees
Bebo White, Topher White, Umar Kalim, Les Cottrell - SLAC
Naman Madan, aayush.2896@gmail.com, assabitha@amity.edu, jamesdavid.1997@gmail.com - Amity
Method
We will meet by Zoom (see https://zoom.us/). Each attendee will need the Zoom app.
Umar will set up the meeting and notify invitees.
Agenda
Deploying Android PingER
The Android version of the PingER MA, is described with comments at ePingER on Android Native - Amity project (this a proposal/description from Aayush Jain)
- Amity's documents describe a multipurpose, stand-alone device that can be widely distributed, something that we have brainstormed about for a long time.
- Bebo mentioned it to Topher (the Principal Investigator (PI) of the RainForest project) and he feels that the Amity PingER/Android app (when completed and vetted by Topher’s team) could easily be installed as a default service on his rainforest monitors (certainly future ones, not devices already in place). Merging the service data that he already collects with that unique to PingER has the potential to lead to some interesting results.
The topics are:
- How should we proceed?
- We (Topher and the PingER team) agreed to request Amity to share the App and instructions with us; we will look at installing on a jailbroken Android phone at the San Francisco end and try it out.
- We also need to finish up the proxy acquisition of data from the Android MAs. A first step is outlined inhttps://confluence.slac.stanford.edu/display/IEPM/Proxy+support+for+PingER.
- A later step is to look at, evaluate and find resources to implement the ideas expounded in the Future Proposals section of the paper you are working on
Status of Amity MA
The Amity MA is unreliable so using it for a case study does not appear fruitful. A start on such a paper has been made. Les is working with Amity to try and understand this unreliability (emails 10/6/2018, 12/6/2018, 12/23/2018), they say "There is an internet problem we are taking care of it and will get back soon".The ability to gather data from it is very intermittent, It runs fine for several days, then there is no data for many days.
For example:
- From Dec 1 thru Dec 11th we were unable to ping pingeramity.in(202.12.103.71) from December 1 thru December 11 from pinger.slac.stanford.edu. We manually went back and gathered the data.
On December 20th we were unable to ping pingeramity.in from SLAC. Looking in more detail the outage started:
1545191157,12/19/2018 3:45,320.544,320.908,321.415,0 1545192994,12/19/2018 4:16,0,0,0,100 ... and ended: 1545376588,12/21/2018 7:16,0,0,0,100 1545378366,12/21/2018 7:46,319.922,320.940,321.961,0
Since we gather data around 1am PST or 9am GMT this means we were unable to gather data from Amity on 12/19/2018 and 12/20/2018.
- Again we went back and manually collected what we could of the measurements made at Amity MA. Looking at the table of pings from pingeramity.in to www.ncms.ae, we see missing measurements starting just after 3:25am 12/19/2018 until 14:22 12/20/2018.