Static Environments for Prodigy
Static Environments for Prodigy
Prodigy requires
complete knowledge and
consistent domains in which to work.
Thus, although Prodigy could conceivably be applied to dynamic
environments, it is most often applied to problems in which
only its operators, defined in terms of add-lists and delete-lists like
STRIPS, effect changes in the world.
Thus, the world in which Prodigy operates is static and changes only
in response to the application of Prodigy's operators.
These restrictions force Prodigy,
unlike many of the other architectures examined in this document,
to be normally applied to problem domains rather than in-situ,
real-world
problems; i.e., Prodigy works in
simulated environments. These problem domains
consist of a set objects and a set of operators.
The only changes to the environment occur through the
application of operators on objects.
Prodigy problem domains have included:
- The STRIPS domain
- Blocksworld
- Machine Shop Scheduling
- Multi-Agent Robot Planning
- Telescope Mirror Production
- Matrix Algebra Problem Solving
Return to the top of this architecture.
Go to a discussion of this environment
for multiple architectures.
Current Location: Prodigy-Environments-Static