-
Notifications
You must be signed in to change notification settings - Fork 22
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
Survey manager execute goals script #103
Changes from 36 commits
67f9c50
719b744
58176a9
dfb9ad7
796695b
e16eefe
8456b90
ad57def
255143d
a7c09ca
e63ff36
626a51f
1686c12
30c761d
c84eff2
4508014
649ea5c
2647bac
a881ffa
d7ea2f5
e58c7f4
b8ae5aa
2376fc6
fb0c57c
adf0b81
d724113
a11b640
af52e73
362763b
d3d3228
5e89aa4
8038c1f
ab97e93
55d4402
9a3e191
86b7990
8d4f72a
6a18416
8ef602d
efd9ac7
903105c
adf6eb2
4ad2bdd
64e8bf5
12663c3
8b61b23
49add14
c5c76a7
a5ca4c8
d1522ba
29ff61b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,6 +37,51 @@ bays: | |
jem_bay6: [11.0, -9.0, 4.8] | ||
jem_bay7: [11.0, -9.7, 4.8] | ||
|
||
bays_move: | ||
jem_bay1: "-pos '11 -4 4.8'" | ||
jem_bay2: "-pos '11 -5 4.8'" | ||
jem_bay3: "-pos '11 -6 4.8'" | ||
jem_bay4: " -pos '11 -7 4.8'" | ||
jem_bay5: "-pos '11 -8 4.8'" | ||
jem_bay6: "-pos '11 -9 4.8'" | ||
jem_bay7: "-pos '11 -9.7 4.8'" | ||
jem_hatch_to_nod2: "-move -pos '11 -3.5 4.8' -att '0 0 1 90'" | ||
jem_hatch_from_nod2: "-move -pos '11 -3.5 4.8' -att '0 0 1 -90'" | ||
nod2_hatch_from_jem: "-move -pos '11 -1.0 4.8' -att '0 0 1 90'" | ||
nod2_hatch_to_jem: "-move -pos '11 -1.0 4.8' -att '0 0 1 -90'" | ||
nod2_bay2: "-pos '11 0 4.8'" | ||
nod2_bay3: "-pos '10 0 4.8'" | ||
nod2_bay4: "-pos '9 0 4.8'" | ||
nod2_hatch_to_usl: "-move -pos '7.8 -3.5 4.8' -att '0 0 1 180'" | ||
nod2_hatch_from_usl: "-move -pos '7.8 -3.5 4.8' -att '0 0 1 0'" | ||
usl_hatch_from_nod2: "-move -pos '5.3 -1.0 4.8' -att '0 0 1 180'" | ||
usl_hatch_to_nod2: "-move -pos '5.3 -1.0 4.8' -att '0 0 1 0'" | ||
usl_bay1: "-pos '4.7 0 4.8'" | ||
usl_bay2: "-pos '3.65 0 4.8'" | ||
usl_bay3: "-pos '2.6 0 4.8'" | ||
usl_bay4: " -pos '1.55 0 4.8'" | ||
usl_bay5: "-pos '0.5 0 4.8'" | ||
usl_bay6: "-pos '-0.5 0 4.8'" | ||
|
||
# Granite testing | ||
# jem_hatch_to_nod2: "-move -pos '-0.3 -0.1 -0.68' -att '0 0 0'" | ||
# jem_hatch_from_nod2: "-move -pos '-0.3 -0.1 -0.68' -att '0 0 180'" | ||
# nod2_hatch_from_jem: "-move -pos '0.3 -0.1 -0.68' -att '0 0 0'" | ||
# nod2_hatch_to_jem: "-move -pos '0.3 -0.1 -0.68' -att '0 0 180'" | ||
|
||
maps: | ||
jem: "iss.map" | ||
nod2: "isaac.map" | ||
usl: "usl_only.map" | ||
|
||
exposure: | ||
jem: 175 | ||
nod2: 300 | ||
usl: 300 | ||
berth: | ||
berth1: "1" | ||
berth2: "2" | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would note this whole section seems intended for managing inter-module moves using the survey manager, which is outside our agreed scope. Let's not get too wrapped up in working on this yet. Good to note it's isolated into fields of the YAML file that are not used elsewhere yet, so it shouldn't break anything. |
||
bogus_bays: [jem_bay0, jem_bay8] | ||
berths: [berth1, berth2] | ||
robots: [bumble, honey] | ||
|
@@ -53,6 +98,6 @@ stereo: | |
# check purposes. | ||
bound_location: jem_bay4 # The survey flies into bay4 even though it only covers up to bay3 | ||
jem_bay4_to_bay7: | ||
marinagmoreira marked this conversation as resolved.
Show resolved
Hide resolved
|
||
fplan: "jem_stereo_mapping_bay4_to_bay7.fplan" | ||
fplan: "jem_stereo_mapping_bay7_to_bay4.fplan" | ||
base_location: jem_bay7 | ||
bound_location: jem_bay4 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
;; Command was: ./tools/problem_generator.py | ||
;; Working directory was: /home/vagrant/isaac/astrobee/survey_manager/survey_planner | ||
;; Problem template: pddl/jem_survey_template.pddl | ||
;; Config 1: data/jem_survey_static.yaml | ||
;; Config 1: data/survey_static.yaml | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's remember it's not currently in scope to manage inter-module moves with the survey manager. It would be viable to use different static config files for the JEM and USL surveys, and might be simpler. At least we should keep that in mind as an open option. |
||
;; Config 2: data/jem_survey_dynamic.yaml | ||
|
||
(define (problem jem-survey) | ||
|
@@ -246,7 +246,7 @@ | |
;; # conditions and initial state. A likely conops is that the initial version of this file for a | ||
;; # specific activity would be hand-generated, but it might later be automatically regenerated by the | ||
;; # survey manager when a replan is needed (remove completed/failed goals, add retry goals, update | ||
;; # initial state to match actual current state, etc.) See also jem_survey_static.yaml. | ||
;; # initial state to match actual current state, etc.) See also survey_static.yaml. | ||
;; | ||
;; goals: | ||
;; | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
from distutils.core import setup | ||
|
||
from catkin_pkg.python_setup import generate_distutils_setup | ||
|
||
d = generate_distutils_setup(packages=["survey_planner"], package_dir={"": "tools"}) | ||
|
||
setup(**d) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole section is implementing features that are out of scope, so I don't want to encourage more work on this right now.
But here are some thoughts for improvements if we are able to add inter-module motion as a stretch goal:
It's too bad many of the positions declared here are copy/paste of position data declared in
bays
above. Probably a cleaner way overall would be to:position
and (optional)attitude
fields.from
andto
position for each move action and could use this info to implement an attitude constraint without exposing this level of detail to the planner.