Unified Way of Serializing Spaces and Samples from Spaces
- Dominant language
- PDDL
- Stars
- 39
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Currently `gym.Spaces` as well as the sample drawn from them are serialized to JSON in different ways producing duplicated code and incompatible formats at a different places of the program.
Known serialization code locations:
* `dacbench.abstract_benchmark.AbstractBenchmark.load_config(...)`
* `dacbench.abstract_env.AbstractEnv.__init__(...)`
* `dacbench.container.container_utils.Encoder` and `dacbench.container.container_utils.Decoder`
Related to #91 and #80
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the serialization paths in dacbench.abstract_benchmark.AbstractBenchmark.load_config(...), dacbench.abstract_env.AbstractEnv.__init__(...), and dacbench.container.container_utils.Encoder and Decoder. Compare how Spaces and their samples are encoded and decoded at each location. Done means these paths use one compatible JSON serialization format without duplicated, conflicting handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100