Get desktop application:
View/edit binary Protocol Buffers messages
Specification of an environment that users interact with. Next ID: 16
Used in: , ,
Unique ID of the environment in the study.
Human readable name of the environment.
Additional instructions for the environment. When a study contains several environments, you can use this field to provide more specific instructions to the user for this environment.
Tf true, then the environment transitions to the next state after an action (e.g. pressing a key). Otherwise, state transitions will happen at a fixed rate, e.g. 15 steps per second.
Maximum number of steps in each episode. If not specified, this will depend on the settings of the environments.
Type of the environment and its settings.
Settings for the Atari environment. See third_party/py/atari_py.
Used in:
ID of the Atari environment, e.g. MontezumaRevenge.
When sticky actions are enabled, the environment repeats the previous action with probability 0.25, instead of playing the action given by the agent.
Settings for the DMLab environments. See third_party/labyrinth/.
Used in:
ID of the DMLab environment, i.e. level, e.g. explore_goal_locations_small.
Settings for the NetHack environments. See github.com/facebookresearch/nle.
Used in:
ID of the NetHack environment, e.g. NetHackScore-v0.
Settings for the Procgen environment. See third_party/py/procgen.
Used in:
ID of the Procgen environment, e.g. maze.
Number of unique levels to generate or 0 to use unlimited levels.
Start level.
Number of levels before resetting the environment.
If true, then levels will advance sequentially.
Seed for random number generation. If not specified, then a random one will be used.
Distribution mode; see DISTRUBUTION_MODE_DICT in procgen/env.py.
Used in:
In exploration mode, number of levels and starting level parameters are ignored.
Settings for the RoboDesk environment. See https://github.com/google-research/robodesk.
Used in:
Name of the task, e.g. open_slide. See config.py for the possible options.
Number of times to repeat each action.
Size of the images in the observations. This would be different from the image renderings that are displayed to the users when collecting the trajectories.
Type of the reward.
Used in:
Settings for the Robosuite environment. See third_party/py/robosuite.
Used in:
ID of the Robosuite environment, e.g. Lift.
Robot(s) to use in the environment, e.g. Panda.
Environment configuration, e.g. single-arm-opposed.
Arm to control, e.g. right or left.
Cameras to use, e.g. agentview or frontview. If empty, then agentview camera will be used.
Controller to use, either IK_POSE or OSC_POSE.
Position scaling for user inputs.
Rotation scaling for user inputs.
If true, then observations will include rendered images.
A study contains a set of episodes provided by the users, i.e. recorded as they interact with the environments in the study. Next ID: 17
Used in:
Unique ID of the episode.
Unique ID of the study that the episode is collected for.
Unique ID of the environment in the study specification.
User that provided the episode.
Unique ID of the session that the episode is part of. Episodes in a session will be from the same user. A user may have multiple sessions.
Starting and end timestamps.
Metadata about the episode, e.g. parameters of the environment.
Number of steps.
Total reward over all steps.
A list of tags for the episode.
Notes about the episode.
ID of the input (e.g. gamepad) controller used by the user, excluding the keyboard (which is always active and can be used together with the controller). This will be the last controller used for an action in the episode in the unlikely case of multiple controllers.
Metadata about the steps of the epsiode keyed by their 0-based index.
State of the episode.
Used in:
Episode completed successfully and confirmed by the user.
Episode is abandoned by the user, e.g. user stopped responding.
Episode is explicitly cancelled by the user before completion.
Episode completed successfully, but at the end the user decided to reject it.
Describes how the episode data was stored.
Used in:
Envlogger. See pypi.org/project/envlogger.
Used in:
Tag directory.
Index of the episode in the logged episodes under this tag directory.
Pickle files.
Used in:
Path of the Pickle file that contains the episode data.
A user session associated with a study.
Unique ID of the session.
Unique ID of the study that the session is associated with.
User of the session.
Starting and end timestamps.
State of the session.
Used in:
Session is valid.
Session is invalid and the corresponding episodes will be ignored.
Metadata about a step of an episode.
Used in:
A list of tags for the step.
Specification of a study. Next ID: 9
Used in: , , , ,
Unique ID of the study.
Name of the study, e.g. "Atari games".
(Short) description of the study.
Instructions for the study. This is shown to the users and should describe the goal of the study and what to do.
User who created the study.
Creation timestamp.
Specifications of the environments in the study. TODO(sertan): We need to define how the environments will be assigned to users, e.g. users may select a list or one of the environments can be chosen randomly.
State of the study.
Used in:
Study is enabled. Users can interact with the environments in the study and provide data.
Study is disabled. Users cannot provide data for the study.
A list of study specifications.
Denotes a tag with a label.
Used in: ,
Label of the tag.
Information about a user.
Used in: , ,
Email of the user.