Thanks for the thread for dicussion.
As a participant who really interested in usng RL to solve this problem, my concerns are:
- Timing. When we use RL, likely we need to use GPU for inference. Unfortuntately, our GPU utilization should be low as it only serve one or a few states per batch. So I may expect that for larger grid size, RL with GPU is likely to be less efficient than OR method.
- Diversity of env. When we have 14 different size of grid, it makes our RL training harder. If we further consider different speeds, it may require more effort for deadlock free planning.
My wishes for Round 2 are:
- Use only a few large test cases(for example, # of test cases <= 10), while keep same overall running time. It may be even better to test with same grid size.
- Use same speed for different agents. I personally prefer to focus more on RL related things, instead of dealing with dead-lock from different speeds.
I think one of ORβs shortage is that itβs not straightforward to optimize for global reward.
My understanding: RLβs advantage is finding a better solution(combining with OR), but not acting in a shorter time.
If we want to see RL performan better than OR, we should give RL enough time for planning/inference on large grid env. (both 5 min and 5s may not be enough for RL to do planning and inference. )