Currently the configurations of an environment depends on gin-configurations. This way have too much possibilities : combinations of the tasks, agent_type, world file, using image or not, image_with_internal_states or not, with language or not...
But many combinations do not work. For example, some tasks do not support some agent_types, some agent does not support image observations, different tasks need different max_steps or step_time...
It would be better to add a default configuration list of Envs, which specifies the combination of the tasks, agent, world file, using image or not, image_with_internal_states or not, with language or not, and give it a name registered to Gym. The CI test also do the tests accrofing to the list.
The list of tasks does not necessarily add all combinations supported. Only the configurations we are using (like the ones used in experiment or in training examples) should be fine. We can add new configuration to the list when necessary at any time.
Currently the configurations of an environment depends on gin-configurations. This way have too much possibilities : combinations of the tasks, agent_type, world file, using image or not, image_with_internal_states or not, with language or not...
But many combinations do not work. For example, some tasks do not support some agent_types, some agent does not support image observations, different tasks need different max_steps or step_time...
It would be better to add a default configuration list of Envs, which specifies the combination of the tasks, agent, world file, using image or not, image_with_internal_states or not, with language or not, and give it a name registered to Gym. The CI test also do the tests accrofing to the list.
The list of tasks does not necessarily add all combinations supported. Only the configurations we are using (like the ones used in experiment or in training examples) should be fine. We can add new configuration to the list when necessary at any time.