-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advice on connection to OpenAI Gym Stable Baseline #6
Comments
Hello Farzan,
Thanks for reaching out, I'm glad its been working for you!
This repo is very much under development, and not in a release-ready state,
still I wanted to make it accessible for willing people like yourself.
I have had a nightmare keeping the repo updated, I haven't pushed to it
since September '21, despite my progress. I would like to get a stable
version out, but I am too busy with my Master's research to put the TLC
into this repo that it deserves.
I will see what I can do in the coming week to push the newest version and
provide some example usage.
You will have to send me what you're trying to do.
The agent/environment interaction-style I chose for EmsPy is very different
from the step() API style of Open AI's Gym API. I did this because (1)
EnergyPlus requires callback function to the running simulation which I
think doesn't adapt well to the step() API flow, and (2) it allows maximal
flexibility in: how you set up your E+ building models, when you collect
data from calling points, how you organize your RL agent's actions and
observations, etc. This flexibility naturally leads to more complexity with
using the API
.
Also, I just couldn't figure out a natural way to adapt things to the Gym
API format, but I am sure there is a way and I am sure you could try figure
it out.
My guess is that to turn EmsPy into a Gym API, you would need to make
strict decisions on how you set up your building model, calling points,
state space, action space, and how you implement your actuation &
observation functions - essentially an API wrapping EmsPy to remove all the
flexibility. Just like how the Gym API's are very rigid and only expose
certain flexibility and MDP variables.
Hope this helps,
Chris
…On Fri, Mar 11, 2022 at 4:11 PM Farz5 ***@***.***> wrote:
Hey mechyAi,
I have been using your code and wanted to thank you for the great work! I
am trying to connect stable baselines to Emspy. I was wondering if you have
any tips or similar codes to share? I would really appreciate your opinion
and help!
Best,
Farzan
—
Reply to this email directly, view it on GitHub
<#6>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APTF5CWXGPXFNGMTJANLXW3U7OZHZANCNFSM5QQWI7LA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@Farz5 See https://github.com/mechyai/RL-EmsPy for updated code, repo, and some examples |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey mechyAi,
I have been using your code and wanted to thank you for the great work! I am trying to connect stable baselines to Emspy. I was wondering if you have any tips or similar codes to share? I would really appreciate your opinion and help!
Best,
Farzan
The text was updated successfully, but these errors were encountered: