Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lrs_doc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
lrs2
lrs_doc
Commits
c56a1f4b
Commit
c56a1f4b
authored
1 year ago
by
Tommy Persson
Browse files
Options
Downloads
Patches
Plain Diff
Fixing documentation.
parent
9c812182
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+12
-10
12 additions, 10 deletions
README.md
with
12 additions
and
10 deletions
README.md
+
12
−
10
View file @
c56a1f4b
...
...
@@ -293,16 +293,18 @@ each factories from a laucnh file the main function is needed.
An executor can be of a type were the node is expanded before
execution of the node. The expansion must be of a type that assigns
execution units to all the new nodes created in the expansion and the
expansion must be able to be done before we start the execution of the
whole TST tree. Also if the node to be expanded is on unit X then all
non-terminal noded need to have X as execution unit.
There is an tree execution server on all agents that takes a service
call with the whole JSON tree to expand. The first step in this
execution is to expand the terminal node that should be executed on
the agent running the execution tree. The actual expansion is done in
the ExecutorFactory class for a node type.
execution units to all the new nodes created in the expansion. The
expansion of terminal nodes will be done during execution. Also if
the node to be expanded is on unit X then all non-terminal noded need
to have X as execution unit.
There is an tree execution server on all agents. That node handle the
execuion of a tree. This node will start by expanding the tree with
the parts that are executed on the same agent. Remotely executes
terminal node will be possibly expanded during execution. There is no
longer the concept of a global TST tree which was used in the ROS1
implementation).The actual expansion is done in the ExecutorFactory
class for a node type.
Example of how to implement an expandable executor for in-air-goal:
```
python
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment