Skip to content
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

The published code is not for A3C model, but for REINFORCE ? #12

Open
amrous opened this issue Jan 2, 2023 · 1 comment
Open

The published code is not for A3C model, but for REINFORCE ? #12

amrous opened this issue Jan 2, 2023 · 1 comment

Comments

@amrous
Copy link

amrous commented Jan 2, 2023

First, I would thank you for publishing this very good work. It helps me a lot in many points.
After analysing the code for more then 3 monthes, and make it works,
I think that the code that you have published is for reinforce methode and not for A3C one.

I'm trying to work on it, to implement the A3C method, but my big problem, is that i can't identify where i must implement the asynchronized actors, and what is their signification in the cloudsim.

Thanks

@Laicize
Copy link

Laicize commented Feb 20, 2024

First, I would thank you for publishing this very good work. It helps me a lot in many points. After analysing the code for more then 3 monthes, and make it works, I think that the code that you have published is for reinforce methode and not for A3C one.

I'm trying to work on it, to implement the A3C method, but my big problem, is that i can't identify where i must implement the asynchronized actors, and what is their signification in the cloudsim.

Thanks

Hello, I am a graduate student from Shanghai, and I am also reproducing this paper, but I found that this engineering code may not be the author's final code. I am still revising the relevant code. Can you share your working code? Conduct related study and comparative analysis?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants