Coder Social home page Coder Social logo

lbnl-eta / lpdm Goto Github PK

View Code? Open in Web Editor NEW
3.0 15.0 1.0 3.75 MB

Local Power Distribution Manager (LPDM)

License: Other

Python 54.97% Dockerfile 0.13% Makefile 0.51% JavaScript 24.69% Shell 0.16% HTML 16.79% CSS 2.59% Batchfile 0.11% Pug 0.04% Sass 0.02%

lpdm's Introduction

LPDM

Local Power Distribution Manager (LPDM) is a transactive energy microgrid controller implemented in the VOLTTRON distributed control platform. The system uses the price of electricity as the mechanism for conducting transactions that are used to manage energy use and to balance supply and demand. In order to allow testing and analysis of the control system, the implementation is designed to run completely as a software simulation, while allowing the inclusion of selected hardware that physically manages power. Equipment to be integrated with the microgrid controller must have an IP (Internet Protocol)-based network connection and a software “driver” must exist to translate data communications between the device and the controller. Sample hardware drivers are in a companion repository called LPDM-Drivers. VOLTTRON-specific integration code is in another companion repository called LPDM-Volttron.

lpdm's People

Contributors

alexbroughton avatar anandkp92 avatar anna-liao avatar dependabot[bot] avatar judekratzer avatar mspears-lbl avatar stephenczarnecki avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

phgupta

lpdm's Issues

Create utility meter agent

From Christian:
Create an agent that publishes a price and consumption periodically. Make the grid controller listen to this price, and if the GC receives no price, it should assume that the grid is down, and switch over to the generator. The GC sets the price for the utility meter power at a very high level when it receives no signal, so that the GC automatically won’t use the grid as an energy source.
Read the price from a file for right now. In the future it will be a web feed.
Provides power consumption at meter (average over last 5 minutes)

Test: create scenario with a utility meter, GC and diesel generator and dummy EUD with load. Then trigger a grid outage, by either stopping the utility meter agent, or ‘telling’ it that there is a grid outage (need to come up with a mechanism), and see if the fuel level declines.

Write Dockerfile that runs this test.

One of your dependencies may have a security vulnerability

@CJKohler / @StephenCzarnecki -- I am putting this in an issue because I don't know who all the contributors are. Maybe you already got this email, but here is the content -- there were several of them

  LBNL-ETA/LPDM
Known moderate severity security vulnerability detected in morgan < 1.9.1 defined in package.json.package.json update suggested: morgan ~> 1.9.1.Always verify the validity and compatibility of suggestions with your codebase. Known moderate severity security vulnerability detected in morgan < 1.9.1 defined in package.json.
Known moderate severity security vulnerability detected in morgan < 1.9.1 defined in package.json.
package.json update suggested: morgan ~> 1.9.1.
Always verify the validity and compatibility of suggestions with your codebase.
  LBNL-ETA/LPDM
Known high severity security vulnerability detected in Jinja2 < 2.10.1 defined in requirements.txt.requirements.txt update suggested: Jinja2 ~> 2.10.1.Always verify the validity and compatibility of suggestions with your codebase. Known high severity security vulnerability detected in Jinja2 < 2.10.1 defined in requirements.txt.
Known high severity security vulnerability detected in Jinja2 < 2.10.1 defined in requirements.txt.
requirements.txt update suggested: Jinja2 ~> 2.10.1.
Always verify the validity and compatibility of suggestions with your codebase.
  LBNL-ETA/LPDM
Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.5defined in requirements.txt.requirements.txt update suggested: paramiko ~> 2.1.5.Always verify the validity and compatibility of suggestions with your codebase. Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.5defined in requirements.txt.
Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.5defined in requirements.txt.
requirements.txt update suggested: paramiko ~> 2.1.5.
Always verify the validity and compatibility of suggestions with your codebase.
  LBNL-ETA/LPDM
Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.6defined in requirements.txt.requirements.txt update suggested: paramiko ~> 2.1.6.Always verify the validity and compatibility of suggestions with your codebase. Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.6defined in requirements.txt.
Known high severity security vulnerability detected in paramiko >= 2.1.0, < 2.1.6defined in requirements.txt.
requirements.txt update suggested: paramiko ~> 2.1.6.
Always verify the validity and compatibility of suggestions with your codebase.
  LBNL-ETA/LPDM
Known moderate severity security vulnerability detected in requests <= 2.19.1defined in requirements.txt.requirements.txt update suggested: requests ~> 2.20.0.Always verify the validity and compatibility of suggestions with your codebase Known moderate severity security vulnerability detected in requests <= 2.19.1defined in requirements.txt.
Known moderate severity security vulnerability detected in requests <= 2.19.1defined in requirements.txt.
requirements.txt update suggested: requests ~> 2.20.0.
Always verify the validity and compatibility of suggestions with your codebase

Grid Controller upgrade

Modify GC so it can take multiple power sources with each a price, capacity
enabled/disabled state is represented by the capacity, set to 0 if it is disabled.
Conceptually a utility meter is like another generator, generic powersource class
Price blending logic: start with “available” power source with lowest price, max out capacity, add next available more expensive power source, continue up until you meet the load. Need to figure out how to handle battery.
Implement both marginal and average pricing algorithm, with a parameter on the grid controller to indicate which algorithm to use for a given scenario

Create the utility meter class from the “PowerSource” baseclass

https://docs.google.com/a/lbl.gov/document/d/141om3E5fSy1yjgEWe0jHpfPxsP903EpA-zvpqBZDoIU/edit?usp=sharing

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.