Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/solution 2 #4

Merged
merged 4 commits into from
Sep 15, 2024
Merged

Feature/solution 2 #4

merged 4 commits into from
Sep 15, 2024

Conversation

p-rosit
Copy link
Collaborator

@p-rosit p-rosit commented Sep 14, 2024

Changes:

  • BbUnsetParameter calls unset instead of making a new element, seems to work? (Could work with planning to clear inferred params?)
  • Navigate to target location and open it before going to source location
  • Always close location after part has been placed

Comment on lines +61 to +64
self.skill(Selector())(
self.skill("OpenLocation", "", remap={"OpenableLocation": "ObjectTargetLocation"}),
self.skill("Success", ""),
),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to find a neat way around this.
One can probably work with the different preconditions on an implementation of a skill description

skill.setProcessor(SerialStar())
skill(
self.skill("Navigate", "", remap={"TargetLocation": "ObjectTargetLocation"}),
self.skill("BbUnsetParam", "", remap={"Parameter": "StartLocation"}),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These look really ugly. #2 should get some attention

Comment on lines +66 to +70
self.skill("Navigate", "", remap={"TargetLocation": "ObjectStartLocation"}),
self.skill("BbUnsetParam", "", remap={"Parameter": "StartLocation"}),
self.skill("Pick", ""),
self.skill("Navigate", "", remap={"TargetLocation": "ObjectTargetLocation"}),
self.skill("Place", "", remap={"PlacingLocation": "ObjectTargetLocation"}),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is pretty much problem 1. Maybe a "fetch skill" would be a good idea to avoid duplication

@matthias-mayr
Copy link
Owner

I think that one criteria for every "solution" skill could be that one only need to run it once and the problem would be solved. Everything else is done internally.
If that is applied, this skill does not do it yet.

Maybe as a part of that, it would also make sense to make some more knowledge modeling. E.g. waste items and the dumpster could become special.

One other thing to consider is that >= problem 3, actions can fail with some probability and all the skills needed there should take that into account.

@matthias-mayr
Copy link
Owner

I'll merge this for now, since I want to order some files and have some other things to push

@matthias-mayr matthias-mayr merged commit 6d2df71 into main Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants