You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lama planner will return and store the plan results to the "sas_plan.ipc" files. When dealing with the PDDL problem with cost syntax, the results can be multiple with different total cost. Please check the demonstration section of this video: https://www.youtube.com/watch?v=-nD5qpk508w
It would be great to have a manifest for what features the planner can provide, so that the user can choose what kind of result they want. For example, all plans will be returned if users want all results, and if users want the optimal result, the plan with minimum total cost will be returned.
The text was updated successfully, but these errors were encountered:
Currently, the planning-as-a-service is using lama and bfws as planners (According to the deployment record: https://drive.google.com/file/d/1El1v53_h5BlfT0K3PaCIgr_oBSmPRpbT/view?usp=sharing).
The lama planner will return and store the plan results to the "sas_plan.ipc" files. When dealing with the PDDL problem with cost syntax, the results can be multiple with different total cost. Please check the demonstration section of this video: https://www.youtube.com/watch?v=-nD5qpk508w
It would be great to have a manifest for what features the planner can provide, so that the user can choose what kind of result they want. For example, all plans will be returned if users want all results, and if users want the optimal result, the plan with minimum total cost will be returned.
The text was updated successfully, but these errors were encountered: