dpinney / omf Goto Github PK

• Add evcharger object to components.
• Build an example analysis with it.
• Debug.

This should be informed by the monetization work.

But as it is:

• Survey openei.org for datasets that might improve our analysis.
• Figure out how to extract and load the data.

TJ Did a good survey (below).

• Gotta merge Feeder-Calibration branch. Watch out for duplicate copies of some of our libraries (e.g. feeder.py).
• Need to have code for running the calibration process as part of the Milsoft import. Includes interface work on home.html.
• Note! Calibration code runs for many hours on even a powerful workstation.

This task borders on impossible.

Now, Milsoft has some kind of ESRI import. If it works as expected, we should leverage that.

TODO: remove browser check, see what happens in non-chrome browsers.

Previously "*40 Platform: iPad support. Hah! We're actually kind of close." Only thing that really doesn't work now is gridEdit. And even that is close to working.

Needs to work with ORNL's giga-scale mapping effort.

nginx (and debian) config, demon strategy, etc.

Two cases (1) hosted service and (2) OMF for download.

• EMTP...
• Matpower from Cornell.
• CEM from UT.
• OpenDSS.

A faster means of doing what-if analysis.

Ideally, we'll move to a different analysis view that will make re-running analysis much faster and easier.

1. Make delete/edit buttons not all crooked and stuff.
2. When we need to scroll, don't scroll the header and footer where the buttons are.
3. Use nice unicode crosses instead of Xes for the delete attribute buttons.
4. Nice-to-have: make the css+html really clean and easy to understand.

This needs to work with ORNL's giga-scale mapping effort. #36

TODO

1. One-page explanation for non-Python programmers.
2. Anything in omfDesign that needs to go in the wiki?
3. Get all the wiki pages in decent shape.

Goal

Find a map that runs in a browser that (1) displays 1 million vector features (lines and polygons) and (2) is editable.

Most Promising Leads

• Polymaps with image tiles. Demo here. We've tried with progressively-loading vectors but we still have problems with single feeders with 100,000 features.
• Open Street Maps editor. Demo here. They show image tiles until you get very close, at which point they load vector features. Great performance for a billion (trillion?) feature dataset.

We can already get stddev from gridlab.
What chart to use? http://www.highcharts.com/demo/area-basic
What models is this for? GridlabMulti (then quick port to solarEngineering and cvrDynamic).

1. Do usability testing with beta community.
2. Enable analysis editing.
3. Move to a single interface for report and study viewing and editing.
4. Improved home screen.

Looked into expanding existing report, found cost-based approach clearest, opening new issue in future event for revenue-based approach.

Needs to work with ORNL's giga-scale mapping effort.

• A report that shows the feeder and colors according to voltage.
• Allow stepping through time to show changes.
• Heatmap? Or colored single-line diagram?
• Allow quantities other than voltage. Current, yes. Power consumption?

Doug Danley is putting together comments on this subject.
dpinney will collect feedback from other beta participants.