-
Notifications
You must be signed in to change notification settings - Fork 71
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
[WinError 267] The directory name is invalid #37
Comments
Indeed I faced the same issue. Maybe a PR on the Environment https://github.com/prosysscience/JSSEnv is needed which provides a less OS-dependent implementation. This needs to cover the following areas:
|
Hi there, Thank you for sharing this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Pierre Tassel,
Thank you very much for sharing your implementation of RL based solution for Job Shop Scheduling Problem. This really helps students like me who are learning RL implementations that address real world problems.
While I was trying to get the code working on my pc (Windows 10 laptop), I encountered the below issue:
Exception has occurred: NotADirectoryError
[WinError 267] The directory name is invalid: 'C:\Users\pg/ray_results\PPO_JSSEnv:jss-v1_2023-01-15_08-54-17l2jg9jkq'
File "C:\Users\pg\RL-Job-Shop-Scheduling-master\JSS\main.py", line 152, in train_func
trainer = PPOTrainer(config=config)
File "C:\Users\pg\RL-Job-Shop-Scheduling-master\JSS\main.py", line 165, in
train_func()
I'm suspecting this is due to windows o/s doesnt support creating folder with a colon (:) character in the folder name, as the PPOTrainer( ) tries to create a folder with the environment name (JSSEnc:jss-v1) as a part of it.
Can you please let me know how I can address this issue? I tried without the JSSEnv: prefix, but then it is unable to recognize the environment name. Some solutions on the web talk about implementing a custom logger which doesnt seem to be straight forward. Is there a simpler workaround for this issue?
Regards,
Prasanth
The text was updated successfully, but these errors were encountered: