Containerized Visualization + ChatGrid #147
Conversation
|
Thanks, @nedpfeiffer. @sichenjin : Can you please take a look at this pull request. @cameronrutherford : Can you take a look at this and see if this can be added/merged to the ExaGO docker instance? |
The existing Docker configuration for ExaGO is a mix of our GitHub container registry (ghcr) deployment, as well as the For the ExaGO deployment in the EIOC Virtual Machine, I modified the Dockerfile in In future, once we have a ghcr version of ExaGO w/o the need for CoinHSL, both the Docker compose and devcontainer can be changes to just use that deployment. |
viz/README.md
Outdated
| First, we need to convert the ExaGO output `.json` files to `.csv` files. The difference between the two data formats is that JSON stores attributes and values as dictionary pairs but CSV stores attributes and values as tables. You can write your own script for this conversion or use the provided script. | ||
|
|
||
| To use the provided script, first copy the ExaGO output `.json` file to the `viz/data` subdirectory and simply run the following script in the `viz/data` subdirectory (replace the example filename with your json filename). This will output three CSV files: `generation.csv`, `bus.csv`, and `tranmission_line.csv`. | ||
| ``` | ||
| python jsontocsv.py opflowout.json | ||
| ``` |
There was a problem hiding this comment.
@abhyshr iirc we discussed adding direct CSV output support to both ExaGO and the Python bindings at some point, but were satisfied with this approach (post-processing based conversion). Should we open an issue explicitly to track this?
|
This is awesome, @nedpfeiffer! The setup process has been greatly simplified, and I really appreciate it. I tested it locally, and the visualization works perfectly. However, could you provide more details on how the database is currently connected to the backend? I followed the instructions to edit the setup.env file, but it seems ChatGrid can't read the database information correctly. Additionally, I'm not very familiar with Docker. Is it possible to access the backend output for debugging when running the code in Docker? Thank you. |
Docker configures a default virtual network and automatically resolves hostnames to the names of the containers. In
Please make sure you've run
I took a cursory look at this and haven't found an easy solution such as adding |
Merge request type
Relates to
This MR updates
Summary
I containerized the ExaGO visualization + ChatGrid with Docker Compose, simplifying set up. I also updated the documentation.
These proposed changes will break existing manual installations and will force users to switch to Docker Compose. I had to edit
viz/backend/sqlchain.pyandviz/backend/config.pyto get the backend and database containers communicating. If there's an approach that won't break existing manual installs, I'm happy to try to tackle that.