Open n30111 opened 1 year ago
@hora-anyscale can you please share whats the conclusion here? Is it user error?
@ArturNiederfahrenhorst ^^^
Hi @n30111 Thanks for raising this I'm working on a solution.
@ArturNiederfahrenhorst
I am also getting an error regarding enable_connectors, and if I set enable_connectors=False, the error does not occur.
The error is different from this issue, but I am asking here because the content may be related. What is the background of enable_connectors=True being default after updating to Ray ver 2.3?
I see, I think we should simply deprecate these APIs altogether. Actions should be computed on individual Policies (old stack) or RLModules (new stack) only. These APIs are too leaky and not well defined (multi-agent vs preprocessor vs ...).
For now, as a quick workaround, could you simply use:
algo.compute_single_action(obs)
instead?
In case you need a certain policy (in a multi-agent case, you can also do):
algo.compute_single_action(obs, policy_id=[xyz])
What happened + What you expected to happen
When running inference or computing actions using an instance of algorithm,
algorithm.compute_actions
, with connector API enabled, it throws error.The same issue does not occur with
config["enable_connectors"]=False
Versions / Dependencies
Ray=2.3
Reproduction script
Issue Severity
Medium: It is a significant difficulty but I can work around it.