simulating distributed energy appliances in a virtual power plant
Documentation of the VPP Model structure
For the simulation of the virtual power plant a basic data structure is developed. This structure is designed in such a way that there are three superordinate elements.
The Component class represents a component within the virtual power plant. This can be, for example, a photovoltaik system or a combined heat and power plant. In addition to the generators, consumers and electrical storage devices can also be stored in this way. The different generators, consumers and storages are derived from the Component superclass. The superclass is used to provide general functionality for the accounting of the power flows within the virtual power plant. Therefore, it does not matter whether an electricity storage device or a photovoltaik system is to be balanced afterwards. However, you can create derivations from this object so that you can still represent the special features of the individual components.
The Component class requires the implementation of the following function. Def observations_for_timestamp(self, timestamp) This function takes a timestamp and returns a key-value-paired dictionary which contains the possible observations of that particular component. A energy storage device can, for example, return a dictionary with the key state of charge and a value for that key. The operator of the virtual power plant can use this information to derive actions from this.
The controlling functions are individual for each derived Component. A energy storage device, for example, can provide functions to charge and discharge energy. A combined heat and power plant on the other side can offer functions for ramping up or ramping down.
The third unification based on Component are the balancing functions. By having a unified function for balancing power flows there is no need to distinguish between different components. Def value_for_timestamp(self, timestamp) This function returns the value at a given timestamp. The return value is a floating point. A positive float represents a consumption, a negative float a generation. This function gets called in each iteration of the simulation to sum up the generation and consumption. This result gets compared to the target sum of the virtual power plant at this timestamp.
Virtual power plant
The second superordinate element is the VirtualPowerPlant object. This represents a combination of different components. Individual components can be added and removed for the simulation. By this encapsulation of the individual components, different topologies of the virtual power plant can be simulated.
The last element to be named is the Operator object. This object receives a reference to a VirtualPowerPlant object and controls this according to the stored logic. This element can also be used as a basis to achieve different goals. By deriving this class one Operator can, for example, aim to maximize the share of renewable energies. Another Operator could maximize the monetary profit.
The Environment class is an encapsulation of every environmental impact on the system. In addition to basic weather data, it is also possible to store regulatory framework conditions for the operation of a virtual power plant. The Environment can be passed to any Component in the constructor. Depending on the component, individual data is accessed.
The UserProfile class is similar to the Environment class. However, this contains information on the respective usage of different types of users. For example, it can be stored how many kilometers per day an electric vehicle covers. This information is used, for example, in the model of the electric vehicle to calculate the state of charge at arrival in the evening. Further parameters which describe the user behavior can also be stored.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size vpplib-0.0.1.tar.gz (22.8 kB)||File type Source||Python version None||Upload date||Hashes View|