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

Setup isues #1

Closed
Hussien-Aboelnaga opened this issue Jun 13, 2024 · 2 comments
Closed

Setup isues #1

Hussien-Aboelnaga opened this issue Jun 13, 2024 · 2 comments
Assignees

Comments

@Hussien-Aboelnaga
Copy link

Helo Luke,

Hope you are doing well,

Thank you very much for this code and the idea. It is very interesting.

I have tried to use this code in my machine but i can not. I tried different ways but with no luck. Here is the output after i tried to run the expermients.
BTY: i am using WSL2 which is a toll to run ubuntu linux system on windows.

image
image

Would you please help me to know what should i do?

Thank you.

@LukeVassallo LukeVassallo self-assigned this Jun 14, 2024
@LukeVassallo
Copy link
Owner

Hi,

The development work was carried out on an Ubuntu 20.04 machine. Tests are run regularly on the code base so I suspect the issues raised are coming from WSL. You can check the test results and auto generated reports here: https://gitlab.lukevassallo.com/luke/rl_pcb/-/pipelines/403.

There seems to be a problem with the running of experiments as indicated by the mkfifo command. You may need to comment out the scheduler in run.sh (line 20) and manually start each experiment. The purpose of the scheduler is to run multiple experiments in parallel on different operating system processes.

The hyperparameter files hp_td3.json and hp_sac.json are soft relative links that point to the RL_PCB/defaults. Can you confirm that these link are present on your system in RL_PCB/experiments/00_parameter_exeperiments/hyperparameters ?

The missing hyperparameter files seem more critical. I would try to resolve those errors first and then check the scheduler if problems still persists.

Hope this helps!

@LukeVassallo
Copy link
Owner

Since there has been no activity on this issue for a while I'm assuming that it has been resolved. If otherwise please feel free to open a new one.

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