Summary of 3/29/11 meeting

2 views

Skip to first unread message

Philip Johnson

unread,

Mar 29, 2011, 8:29:32 PM3/29/11

to wattdep...@googlegroups.com

Summary of 3/29/11 meeting:

(1) create a new directory called "public" and put the file in there (without any version number). Send that URL off to Google.

Not done. Will do this after we find out from Robert the best way to specify both the REST and the Google visualization URLs in one form field.

(2) Convert to google visualization API for calculated data.

In the paper, Yichi did some performance measurements that demonstrated that the google visualization API is significantly faster than the REST API when there are more than about a dozen data points.

The downside is the potential need to have to specify 2 URLs in the configuration panel: one for the REST API and one for the visualization API.

Question for Robert: is it possible to automatically deduce the visualization URL given the REST API URL. We would prefer to not force the user to have to specify two URLs. Robert: please send email with your comments.

(3) add a drop-down menu to the PlotMonitor window that allows the user to select a different source.

Done!

(4) Paper review

Next steps for paper:

(a) provide more structure: table of contents, sections, subsections, and subsubsections...

(b) insert screen images to illustrate system, architectural or design diagrams, etc.

(d) develop test cases and build and document procedure in paper. Include output of shell/console window to illustrate execution.

(e) Recommendations for improvements to WattDepot:

- Provide an XML interface to obtaining sequences of energy/power data.

- Reason: no need to provide 2 URLs to obtain complete functionality of library.

Robert S Brewer

unread,

Apr 1, 2011, 10:05:50 PM4/1/11

to wattdep...@googlegroups.com

On Tue, Mar 29, 2011 at 2:29 PM, Philip Johnson <philipm...@gmail.com> wrote:

Summary of 3/29/11 meeting:

(1) create a new directory called "public" and put the file in there (without any version number). Send that URL off to Google.

Not done. Will do this after we find out from Robert the best way to specify both the REST and the Google visualization URLs in one form field.

Looking forward to seeing it in the Google directory :)

(2) Convert to google visualization API for calculated data.

In the paper, Yichi did some performance measurements that demonstrated that the google visualization API is significantly faster than the REST API when there are more than about a dozen data points.

The downside is the potential need to have to specify 2 URLs in the configuration panel: one for the REST API and one for the visualization API.

Question for Robert: is it possible to automatically deduce the visualization URL given the REST API URL. We would prefer to not force the user to have to specify two URLs. Robert: please send email with your comments.

The convention to date has been to locate the Google Visualization API port 2 greater than the REST API port. So I think for our purposes here it is fair to just specify the REST API URI and generate the other one by adding 2 the port #.