In aa2008858140fd0a10528c81f63229b6dc70956a, I committed @AlexAntn 's work based on the PRADA probabilistic planner.
It is composed of two software bundles:
the actual planner module, planner.exe, which needs to sit in the same directory of these files: config, rules.dat, state.dat, symbols.dat (currently this directory is app/conf)
a bunch of Python scripts C++ modules, which need access to these files (they can be anywhere on the system): Object_names-IDs.dat, pre_rules.dat, pre_symbols.dat, subgoals.dat
[ ] put planner.exe + its files in a dedicated directory instead of app/conf
[ ] rename the "config" file to avoid confusion with other modules' configurations
[x] the Python scripts should use ResourceFinder in order to locate the files to load/save, instead of using the current directory
[x] each Python script planner module should create yarp ports with a clear prefix unique to that script, for example geometric_grounding.py should create ports called /geometricGrounding/* (or similar)
[x] ideally, the user should be able to override the default prefix with a --name parameter (this has low priority)
[x] port names in the modules & XML launchers should use a consistent style, for example always camelCase or always names_with_underscore, not a mixture of the two
In aa2008858140fd0a10528c81f63229b6dc70956a, I committed @AlexAntn 's work based on the PRADA probabilistic planner.
It is composed of two software bundles:
Python scriptsC++ modules, which need access to these files (they can be anywhere on the system):Object_names-IDs.dat,pre_rules.dat, pre_symbols.dat, subgoals.datTracker of improvements to make:
the Python scriptsshould use ResourceFinder in order to locate the files to load/save, instead of using the current directoryPython scriptplanner module should create yarp ports with a clear prefix unique to that script, for example geometric_grounding.py should create ports called /geometricGrounding/* (or similar)cc @lorejam @vicentepedro