Closed pmdoll closed 7 years ago
Note: PLANVIZ calls the plan-schema merge operation upon loading plans, thus this is really a plan-schema issue:
tmarble@cerise 131 :) ./bin/plan-schema -i ../pamela/test/pamela/HTN/parallel.feasible.htn.edn \
-i ../pamela/test/pamela/HTN/parallel.feasible.tpn.edn \
-o parallel.feasible.merge.edn merge
Reading input from: ../pamela/test/pamela/HTN/parallel.feasible.htn.edn
Reading input from: ../pamela/test/pamela/HTN/parallel.feasible.tpn.edn
DEBUG END NODE :parallel.feasible.tpn:node-58 NOT FOUND?
DEBUG END NODE :parallel.feasible.tpn:node-67 NOT FOUND?
DEBUG END NODE :parallel.feasible.tpn:node-73 NOT FOUND?
tmarble@cerise 132 :)
Ok, what is the issue? What is plan-schema trying to do here during the merge operation?
This is an old debugging statement that can probably go away.
Closed by https://github.com/dollabs/plan-schema/commit/d6160aa23c4088c3f83d0df592dc9f2d61fe10c5
NOTE: PAMELA and PLANVIZ build.boot will need to be updated with this version of plan-schema.
Planviz is complaining about end-nodes.
In
pamela/test/simple-choice-parallel
In the generated tpn file, state nodes have an end node. Only the state nodes that represent beginning of a
actual sequence
should have end node slot. i.e (sequence (act1) (act2)) and not otherwise