PageRenderTime 30ms CodeModel.GetById 15ms RepoModel.GetById 0ms app.codeStats 0ms

/external.md

https://gitlab.com/ijlopez-phd/instructions
Markdown | 40 lines | 23 code | 17 blank | 0 comment | 0 complexity | 87da3e0da058e2833661a95ea770e860 MD5 | raw file
    

  1. 

  2. # External resources
    3. 

  3. 

  4. <br>
    5. 

  5. ## GridLAB-D simulator
    6. 

  6. 

  7. The platform uses [GridLAB-D](http://www.gridlabd.org/) in order to simulate the electrical grid. Specifically, the version 2.3 is used. **It is important to highlight** that that the modules have not been tested with the version 3.0, which is the current stable version of GridLAB-D (it had not been released at the time of developing the project).
    8. 

  8. 

  9. GridLAB-D has an active developer community and forums where users can ask and find all necessary information. Useful links on GridLAB-D can be found [here](http://www.gridlabd.org/resources.stm).
    10. 

  10. 

  11. <br>
    12. 

  12. ## XMPP Server
    13. 

  13. 

  14. The communication between the simulator and software agents is carried out using the XMPP protocol, as indicated in the OpenADR 2.0 standard. To this end, we use the server [Openfire](http://www.igniterealtime.org/projects/openfire/), although any other standard server is valid.
    15. 

  15. 

  16. The server must be configured in order for users can automatically create new accounts. In practice, by using the user interface provided by the software package, it is only necessary to create the account of the Grid Operator. In this regard, the default configuration file expects the following data:
    17. 

  17. 

  18.   * __Username__ : gridoperator
    19. 

  19.   * __Password__: gridoperator1
    20. 

  20.   * __Resource__: asmarket
    21. 

  21. 

  22. Later, the application that implements the Grid Operator creates dynamically the users required by each simulation. This is why is so important that the server is configured so that users (and in special the Grid Operator user) are allowed to create new accounts.
    23. 

  23. 

  24. Furthermore, the default configuration file also sets the following values for the XMPP server:
    25. 

  25. 

  26.   * __Url__: localhost
    27. 

  27.   * __Port__: 5222
    28. 

  28. 

  29. If any of the above values is not going to be used, a new configuration file must be created. See the [Configuration](/configuration.md) section.
    30. 

  30. 

  31. <br>
    32. 

  32. ## Database system
    33. 

  33. 

  34. The application uses two databases for the simulations. One is for storing control information on entities such as _scenarios_ and _simulations_. The other database stores demand estimations used by the software agents in order to plan their actions.
    35. 

  35. 

  36. It is recommended to use [PotsgresSQL](http://www.postgresql.org/) to store the information. Specially, PostgreSQL is important to store the demand estimations, which consist of a large amount of data. In case you want to use another database system to this end, the Python scripts that create and store the estimations should be changed.
    37. 

  37. 

  38. In order to test the application, the installation of  [HyperSQL (HSQLDB)](http://hsqldb.org/) is also recommended. This is a light database system that facilitates testing the application with little overhead. However, it should be noted that HSQLDB is not a valid storage system for the demand estimations, as it is unable to handle so much data.
    39. 

  39. 

  40. By default, PostgreSQL is used for both to store the control information and the demand estimations, even though this condition can be easily changed in the configuration files. See [Database](/database.md).
    41. 

  41.