HTN issues - Githubissues

dollabs / pamela

Probabalistic Advanced Modeling and Execution Learning Architecture

Apache License 2.0

233 stars 13 forks source link

Closed pmdoll closed 7 years ago

pmdoll commented 7 years ago

For first.pamela, When using htn task,

We should be able to create HTN from pamela class first-tpn instead of first-tpn-htn
in between constraints are not created
Bounds are not created for plant activities
Appearance of labels is unexpected and misleading.

first cfm

first htn

dcerys commented 7 years ago

Addressing the 4 points above:

A documented current limitation of the HTN generation is that pmethods cannot have a combination of more than one parallel/sequence/choice. If a 2nd-level parallel/sequence/choice, it's trivial to create a sub-pmethod with the same effect.
It is true that between constraints are not created. Let's create that as a separate issue, so it can be addressed.
The bounds of primitive method declarations is addressed by Issue #98
The appearance of the labels is certainly different. The full display of labels is dependent on Issue #43

Using the HTN-generated version, with the bounds specified at the calling site, we can see (missing the between constraint):

screenshot 2017-05-01 22 06 22

pmdoll commented 7 years ago

Capitalized labels with dashes removed should not be related to pamela. It is a planviz bug or warrants an explanation.

tmarble commented 7 years ago

Addressing each of these points, in turn:

We should be able to create HTN from pamela class first-tpn instead of first-tpn-htn
- incorrect: PAMELA coding convention for HTN proscribes more than one high level combination form.
in between constraints are not created
- addressed in #102
Bounds are not created for plant activities
- addressed in #98
Appearance of labels is unexpected and misleading.
- The "Do A" is a result of the display-name getting set
- The full solution to this problem is blocked on the Name Harmonization bugs:
- plan-schema #22 Approach to handling errors
- pamela #41 Develop new HTN->TPN generation algorithm
- pamela #43 Harmonize TPN and HTN schemas
- planviz #55 Planviz support for name harmonization

dcerys commented 7 years ago

All of the items in this compound issue have been included in separate, individual issues