Why isn the RL-Glue interface object oriented?
RL-Glue is meant to be a low level protocol for connecting agents, environments, and experiments. These interactions can easily be described by the simple, flat, functions calls of RL-Glue. We don’t feel that it is useful to overcomplicate things in that respect. However, there is no reason that an implementation of an agent or environment shouldn’t be designed using an object-oriented approach. In fact, many of the contributors to this project have their own object-oriented libraries of agents that they use with RL-Glue. Some of the codecs even have an OO flavor (Python, Java, Lisp). Some might argue that it makes sense to create a codecs that support very seriously, with a hierarchy of observation and action types, where you create an instance of RL-Glue instead of calling static methods on it, etc . This would not be hard, it’s just a matter of someone interested picking up the project and doing it. Personally, we’ve found it easy enough to write a small bridge between the existing
Related Questions
- Is the school mainly oriented towards long stays, i.e. do they object to someone (who doesn speak Chinese and is no good at Tai Chi) popping in for a week or so?
- Why am I having an InvalidClassException thrown during the serialization of my object which implements the Externalizable interface?
- Why object oriented software development process difference from conventional software development?
