icyphy
Sprint Alpha demo
Note: the issue was created automatically with bugzilla2github tool
Original bug ID: BZ#485 From: Elizabeth Latronico <[email protected]> Reported version: 8.1.devel CC: [email protected]
Depends on: BZ#487, BZ#493, BZ#496, BZ#491 Blocker for: BZ#484
Main demo for our first sprint.
Note we should still have smaller test cases/test models for each of the individual features.
Created attachment 41 Temperature Alert app - main screen
Attached file: SprintAlphaDemoMain.png (image/png, 78183 bytes) Description: Temperature Alert app - main screen
Created attachment 42 Temperature Alert app - URL view
A single screen can pull data from multiple web services (assuming one web service is mapped to one URL). Some sample URLs are shown here.
Attached file: SprintAlphaDemoURL.png (image/png, 113021 bytes) Description: Temperature Alert app - URL view
Bonus tasks: Bonus: Use a database. This is very interesting, but not top priority. Bonus: Use a consistent RESTful URL naming strategy. This seems like a larger topic. For our first sprint, I think it’s OK to manually define URLs. Bonus: (Next sprint?) Integrate bcvtb to develop a model that can PREDICT the future temperature and send an alert BEFORE there is a problem
Plan 5/10/2012
@ Christopher – Is building square footage data available at that internal Berkeley site? That would be great to show total energy/footage to find the least efficient buildings. https://berkeley.digicality.com/Buildings/Home/Default.htm?Bkey=55
@ Marten – Is the JSON reader almost ready (i.e. by next week), or should we stick with string manipulation for now? Right now the model just reads 1 value. Next it would be good to read a whole day’s worth of values, but this requires changes to handle an array of values. If it’s not close, we could use a file of values in a standard format that Ptolemy can already read.
@ Dai – Could you edit the model so that the model logs an alert message in a Display and sends a mail whenever the energy output of a building exceeds 500 kW? Cory hall should trigger this – I see readings over 500 today. The alert should have the name of the building and the energy output. Max of one alert per building per model execution is good. This could re-use your Ptera model or however you like.
Summary of next features (also uploaded to Bugzilla):
- JSON reader OR file reader to handle arrays
- Alerts
- Test export to web (Beth)
- More buildings once 1), 2) and 3) work
Features after that:
-
Parameter in model so we can toggle between saved data and live data
-
Drill-down model of Cory Hall Pie chart or bar chart using data from Cory Hall CEC Testbed on new.openbms.org – lots of different appliances here Motivation is that it is usually too expensive to cover entire building with sensors, so we can use data from a few sources, plus total energy consumption data, to estimate energy profile of whole building
-
Interactive model using HttpService Be able to set threshold for reporting alerts
I updated org/ptolemy/ptango/demo/UCBPower/buildingsCampusUUID.txt with square foot data. Various data are available via http://dashboard.berkeley.edu/ I have a more details spreadsheet, but I don't want to check it in to svn.
One issue is that identifying building names is tricky between all these databases.
Also, building have either no electrical data or they get torn down (Wheeler Hall was torn down last year)