Open NeoBerekov opened 1 month ago
Are you using the current master branch of PettingZoo? If not, can you try that? I think I changed the behaviour for the nested obs case a while back. If it is still failing with that, can you post code for a minimum env that triggers the api error?
Same issue here. API fails because dict has no dtype. @NeoBerekov did ignoring that particular test work for you?
Seems like it's a reasonable fix to just remove that warning. A PR on that would be very helpful and appreciated. :)
Same issue here. API fails because dict has no dtype. @NeoBerekov did ignoring that particular test work for you?
I'm not sure what is going on when tianshou running its training proc, but it seems that nothing goes wrong when I just ignore that test.
Same issue here. API fails because dict has no dtype. @NeoBerekov did ignoring that particular test work for you?
Did you try this with the current master version from git? If so, do you still get the error?
Question
I am integrating a complex
observation_space
within PettingZoo, adhering to Tianshou framework requirements that necessitate nesting dictionaries withinobservation
to pass observations into a PyTorch model. My environment’sobservation_space
configuration is as follows:During the
api_test
in PettingZoo, I encountered the following errors:The specific failing test code snippet is:
Given the necessity to nest dictionaries for compatibility with Tianshou, which expects PyTorch model inputs, it appears there is a misalignment with PettingZoo’s testing expectations, which presume NumPy array compatibility. How can I reconcile these requirements? Is this an oversight in the
api_test
, or should adjustments be made to accommodate such nested dictionary structures? Any guidance on resolving this configuration mismatch would be highly appreciated.