Package: up-spiderplan
Integration of Spiderplan with the Unified Planning LibraryA constraint-based planning engine for unified planning.Try it out!Note:This requiresdocker desktop >= 4.0.0to be installed (this means that docker compose V2 should be available
viadocker composerather than the stand-alonedocker-compose).Create and activate a Python 3.7 environment. Here we use conda:conda create --name up-sp-test python=3.7
conda activate up-sp-testInstallup-spiderplan:pip install up-spiderplanClone the up-spiderplan repository to get a test case:git clone https://github.com/aiplan4eu/up-spiderplan.git
cd up-spiderplanFinally, we can run the test:python tests/test.pyThis will build and run a docker container that hosts the spiderplan
server. Therefore it will take a bit of time on the first run.Default ConfigurationSpiderplan solves hybrid planning problems by combining preprocessors, propagators and solvers for all required constraint types.
Temporal propgatation is needed even for classical planning because under the hood Spiderplan is a temporal interval based planner.Search space:graphHeuristic:Fast forwardPreprocessors:temporal propagation, constraints processing and operator grounding.Propagators:pruning, domain constraints, temporal constraints, motion planningSolvers:constraint processing, forward goal resolverPlanning Approaches of UP supportedCombined task and motion planning with Reeds Shepp car motion model.Operation ModesOneshot planningVersion History0.6.4 Added Docker Overhead to Result ObjectMeasuring docker overhead for AIPlan4EU evaluationMoving measurement of internal engine time0.6.3 Fixed non-existing folder bugThe gRPC server is now stopped from withing the correct folder if build_docker is set to false.Added a verbose option0.6.2 run_docker option used againRemoved issue where the run_rocker option was ignored for testing purposesAdded option to set build_docker to true to force building docker instead of using the image from docker hub0.6.1 docker-compose backwards compatabilityFixed usage ofdocker composetodocker-composewhich should work (seehttps://docs.docker.com/compose/migrate/)0.6.0 Running SpiderPlan from docker imageFixed issue where the internal engine time would be wrong runUsing image on docker.io instead of building container to reduce time to run for the first time0.5.1 FixesRemoved letter 's' from reported timesFixed issue with new UP test cases0.5.0 Added Internal Engine Time to Result MetricAdding internal engine time to result metric0.4.0 Fixes for Unified Planning 1.0.0 and UP test casesUP dependencyRemoved circular dependency which makes it impossible to load up-spiderplan as a up engine.Fixed EngineImpl to extend OneShotMixin0.3.0 Running the Engine in the UPFix spiderplan grpc server in dockerUse docker to run server through up-spiderplan0.2.0 Motion PlanningMotion planning constraints extracted from UP problemSolve problem with motion constraints and get a plan with pathsFix Spiderplan motion planner to use correct motion modelAllow configuration with available motion planning algorithmsConvert plan into UP plan with motion0.1.0 Basic UP SupportUP problems can be converted to constraint databasesClassical plannningCall spiderplan to produce a solution/failureAnswer translated to a UP resultIssuesWaiting for docker container does not work