Using artificial intelligence automated planning to efficiently execute and evaluate space debris collection
This project uses an AI planning tool known as OPTIC. A ready to use version is included in this project.
The domain of the space debris collection is defined in the following file:
domain.pddl
In order to test the planner, 3 different problems within the domain is defined. These are defined in the following files:
problem1.pddl, problem2.pddl and problem3.pddl
cd <project directory path>
optic-clp.exe -N <domain file name> <problem file name>
Example:
cd C:\Optic
optic-clp.exe -N domain.pddl problem.pddl
optic-clp.exe -N domain.pddl problem2.pddl
Consists of:
- Docks, Landing/Launch pad of rockets.
- Debris bin where debris is disposed off
- Rocket fueling station
- Rockets have to be transported by trucks to the launch pads.
- Debris is taken from rockets to the disposal bin by trucks
- A rocket must first launch and reach a launch point in space then from there it can begin its orbit and enter the grid
- Only a single rocket can launch at any given time from the same launch pad
- The space is modelled by a 3D grid abstraction, consisting of straight line vertices, which are modelled as points, and edges, which are modelled by paths.
- The time taken to travel between points whether straight or curved is defined by the problem designer.
The trajectory of a real rocket is likely to be curved, however this detail is abstracted from the model.
- As the rocket holds a larger number of debris, the mass of the rocket increases therefore the energy consumption rate of the rocket increases.
- The planner can then decide between picking up greater quanties of mass and staying in orbit for longer or returning to Earth and depositing the debris quickly.
- Whilst a rocket is in orbit it can open its solar cells and begin absorbing solar energy from the sun.
Whilst the planner found a solution very quickly in a small state space (4.9 seconds for a single piece of debris), for larger ones the time rose exponentially (167 seconds for 9 debris pieces). Finally, with over 10 pieces of debris the planner simply ran out of memory (as OPTIC for Windows is a 32-bit application it is unable to use more than 4GB of memory).
For this problem the planner successfully split debris collection among the two rockets. There was, however, some time wasted when the truck moves back and forth between the service dock and landing pad.
The planner found a solution in a reasonable amount of time in a small state space, however, for larger ones with over 3 rockets the planner simply ran out of memory due to OPTIC’s limitation being a 32-bit application.
- Problem instances do not scale well with the OPTIC planner, primarily because of its 32 bit limitation with regards to memory usage.
- The plan output by the planner does not always find the most optimal solution, however, in those cases, they are reasonably close to optimal.