You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Qinhua,
I was always struggling to connect the power system simulation tool (like PSAT, BPA) to a public available RL environment like Gym. Your work was amazing. I'd like to know the boundary of the project, mainly on the power system simulation part. To be more specific,
Does the project support electromagnetic transient simulation?
If I'd like to run RL on my own power networks, what part of the case files should I change? And do the model definition files have any documentation to guide me if I want to build my own power network model?
I figure out that the functions you mentioned in Section III.B of your trans paper, like initStudyCase, applyAction, nextStepDynSim were all written in Java in the folder /org/pnnl/gov/pss_gateway. Are the Java files the bridge to connect the RL environment and the power system simulation software? Do you contain the power system simulation software in the repo?
If I'd like to have more actions or build my own rewards, what codes should I change? Are those Java files used to define the actions and rewards?
Thank you again for the great benchmark.
The text was updated successfully, but these errors were encountered:
LeZhengThu
changed the title
RLGC project boundary
RLGC project code structure
Jun 4, 2021
Besides, does the *.jar files in the folder lib contain InterPSS? Where does the power system simulation carry out? I'd like to know more about the power system simulation part so that I can alter that part for my own studies. Thanks.
Dear Qinhua,
I was always struggling to connect the power system simulation tool (like PSAT, BPA) to a public available RL environment like Gym. Your work was amazing. I'd like to know the boundary of the project, mainly on the power system simulation part. To be more specific,
Thank you again for the great benchmark.
The text was updated successfully, but these errors were encountered: