-
Notifications
You must be signed in to change notification settings - Fork 1
MAKE THIS REPO BETTER
James Chojnacki edited this page Jan 8, 2024
·
16 revisions
-
Implement actor - @ray.remote -
Move actor's common parts into actor proto -
ray compatible -
memory parallel collecting is a must, compute is next step -
worker should be remote ( ray actor ) - wrapper -
it should take ref to the cortex model ( ray.put(cortex) ) -
it should take N different instances of environment - can be copied -
replay buffer should be a single instance that stores N collected shards of data from actors -
answer the question about the seed: cortex | policy | env seed. What will happen with const seed? -
env should be remote ( ray actor ) - wrapper -
refactor SC2 environment class together with hydra stuff -
parameters server: https://www.youtube.com/watch?v=XjmbKkc98MA ( 1:09:30 )
get rid of inheritancereplay memory holds rollout trajectoriesray compatible
extract common stuff into coreimplement child node that derives from Cortex protocol
Implement worker which job is to collect dataMove Worker's common parts into worker portray compatible
Implement new Tuner mechanizm for ray
self explanatory
- make this work
- the issue with docker was raised in the pymarl repo: https://github.com/oxwhirl/pymarl/issues/157
Boilerplate codeBad loggingOverall mess
Overall mess
Add SMACV2 supportLink: https://github.com/oxwhirl/smacv2
once ray is integrated make sure MPS and GPU can be utilised for compute
- migrate to Loguru from logging
- link to loguru: https://github.com/Delgan/loguru