About LAPKTLAPKT is an open-source Toolkit written in C++ and Python with simple interfaces that give you complete flexibility by decoupling parsers from problem representations and algorithms. It has been successfully used in embedded systems, webservices, compilations, replanning and contains some of the high-performance planners from the last International Planning Competition 2014.Errandum IPC 2014 Agile track -- Once we fixed the bug on the submission of IPC'8 (International Planning Competition 2014), we were computing h^2 but not using it, our planners BFS_f, DFS+, and SIW+ are the fastest in the AGILE track (minimize CPU time) compared to the last winner, according to our experiments. Planners time, coverage and solution quality media:results_agile_track_2014.pdf you can download the bug-free code media:ipc14-bfs_f_siw_bugfree.tar.bz2 or alternatively go to Download, get the LAPKT sourcecode and at the root of the toolkit use the following scriptLightweight Automated Planning ToolKiTLAPKT_99773a46-da9b-11e7-ac60-784fab18c257Planning CommunityWe welcome anybody in the planning community to contribute into LAPKT, either by just using it or by submitting code implementing stuff they feel should be in an "Automated Planning Toolkit". We only request two things from you. First, to abide to the terms and conditions of the GNU Lesser General Public License (http://www.gnu.org/copyleft/lesser.html). Second, to drop a note on us telling about what you plan to add or what you think should be changed. You can contribute to LAPKT by submitting code or patches to admin@lapkt.org or through the github repository. Forum / public mailing list: LAPKT Google Group (intended for users and non-core developers) internal mailing list: LAPKT-dev Google Group (intended for internal discussions between the core developers) general questions: Miquel Ramirez and Nir Lipovetzky <admin@lapkt.org>Miquel RamirezNir LipovetzkyYour life becomes easier_99773b0e-da9b-11e7-ac60-784fab18c257To enable creation, usage and extension of basic to advanced Automated Planners._99773b90-da9b-11e7-ac60-784fab18c257Open SourceModularitySearch engine components are meant to be modular, allowing users of LAPKT to assemble and combine features of different search engines to come up with customized search strategies, within reason and without sacrificing (much) efficiency.StrategyIn order to do so, LAPKT makes heavy use of C++ templates and the Static Strategy design pattern.PatternsPlanning TasksSeparate search engines from the data structures used to represent planning tasks._99773d48-da9b-11e7-ac60-784fab18c257LAPKT separates search engines from the data structures used to represent planning tasks. This second component receives the name of ‘interface’ since it is indeed the interface that provides the search model to be solved.Existing InterfacesMaintain existing interfaces_99773de8-da9b-11e7-ac60-784fab18c2571At the moment of writing this, the following interfaces are offered:Agnostic ParsingSeparate parsing representation of planning tasks from a representation optimized for off-line planning._99773e74-da9b-11e7-ac60-784fab18c2571.1‘agnostic’: this interface does not depend on a particular planning language, so it is easy to wrap PDDL parsers, separating parsing representation of planning tasks from a representation optimized for off-line planning. This interface should also make easy to integrate STRIPS planners into applications by suitably defining planning tasks programatically.FF ParsingWrap FF parsing components_99773ef6-da9b-11e7-ac60-784fab18c2571.2'ff': this interface wraps FF parsing components to obtain 'agnostic' looking tasks.FD ParsingWrap FD parsing components _99773f6e-da9b-11e7-ac60-784fab18c2571.3'fd': this interface wraps FD parsing components to obtain 'agnostic' looking tasks.Additional InterfacesDevelop additional interfaces._99773ff0-da9b-11e7-ac60-784fab18c2572Future interfaces planned are:VAL InterfaceWrap VAL parser._99774072-da9b-11e7-ac60-784fab18c2572.1'VAL': this interface wraps VAL parser, which supports parsing of PDDL+ features.SAS InterfaceSupport SAS representations natively._997740f4-da9b-11e7-ac60-784fab18c2572.2‘SAS+’: this interface is meant to support SAS representations natively. Since there is no SAS-based planning language, this will probably be useful to integrate planners into applications that are able to define SAS planning tasks programatically.2015-02-162017-12-06http://lapkt.org/index.php?title=Main_PageOwenAmburOwen.Ambur@verizon.net