-
 

bwi_planning package from bwi_planning repo

bwi_planning bwi_planning_icaps14

Package Summary

Tags No category tags.
Version 0.2.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/utexas-bwi/bwi_planning.git
VCS Type git
VCS Version master
Last Updated 2015-04-06
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The planner_krr14 package

Additional Links

Maintainers

  • Piyush Khandelwal
  • Jack O'Quin

Authors

  • Piyush Khandelwal
  • Fangkai Yang
README
No README found. See repository README.
CHANGELOG

Changelog for package bwi_planning

0.2.1 (2014-04-29)

  • added dependency on generated service file. closes #10
  • modified cost_learner to have a unique build name. closes #4
  • Added support for YAML-CPP 0.5+. The new yaml-cpp API removes the "node >> outputvar;" operator, and it has a new way of loading documents.
  • Contributors: Piyush Khandelwal, Scott K Logan

0.2.0 (2014-04-23)

  • Initial release to Hydro.
  • Moved clasp to a separate repository.
  • Fixed bugs while marking door, also added backwards compatible action goto to base action executor.
  • Add missing dependency on gringo.
  • Now print expected next state when observations don't match up.
  • Added an abstract planner.
  • Spring Symposium code is now working.
  • Updating bwi_planning code for the ICAPS 2014 paper.
  • Added ability to track planning times at each iteration.
  • Added a script to run the experiment and reset it as necessary.
  • Fixed heuristics in krr2014 version.
  • Fixed simulation door file. corners no longer needed with the door.
  • Added roslaunch unit test and missing launch run dependencies.

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/example_costs_krr2014.launch
  • launch/environment_krr2014.launch
      • dir_path [default: $(find bwi_planning)/config/simulation]
      • map_file [default: $(find utexas_gdc)/maps/3ne.yaml]
      • location_file [default: $(arg dir_path)/locations.yaml]
      • door_file [default: $(arg dir_path)/doors.yaml]
  • launch/example_incomplete_krr2014.launch
  • launch/experiment_no_costs_krr2014.launch
  • launch/planner_krr2014.launch
      • initial_file [default: $(find bwi_planning)/experiment/initial]
      • domain_costs_file [default: $(find bwi_planning)/domain/cost]
      • domain_semantics_file [default: $(find bwi_planning)/domain/nav]
      • query_file [default: $(find bwi_planning)/experiment/query]
      • costs_file [default: $(find bwi_planning)/experiment/distances.lua]
      • rigid_knowledge_file [default: $(find bwi_planning)/domain/experiment]
      • planning_times_file [default: /tmp/planning_times.txt]
      • clingo_timeout [default: 60]
      • clingo_steps [default: 15]
      • dry_run [default: false]
      • auto_open_door [default: true]
      • use_cost_optimization [default: false]
      • enable_learning [default: false]
      • enable_artificial_delays [default: false]
      • artificial_delay_file [default: $(find bwi_planning)/config/kitchen_delay.yaml]
  • launch/cost_learner_krr2014.launch
      • dir_path [default: $(find bwi_planning)/config/simulation]
      • door_file [default: $(arg dir_path)/doors.yaml]
      • costs_file [default: /tmp/distances.lua]
      • values_file [default: /tmp/values]
  • launch/experiment_krr2014.launch
      • costs_file [default: /tmp/distances.lua]
      • enable_artificial_delays [default: false]
      • artificial_delay_file [default: $(find bwi_planning)/config/kitchen_delay.yaml]
      • query_file [default: $(find bwi_planning)/experiment/query]
      • clingo_timeout [default: 60]
  • launch/experiment_incomplete_krr2014.launch
  • launch/example_krr2014.launch

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged bwi_planning at Robotics Stack Exchange