You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tesseract/tesseract_planning/tesseract_process_managers/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,12 @@ This package contains process managers for Tesseract. Examples include
6
6
* Raster strip planning manager
7
7
8
8
## Overview
9
-
### ProcessInput
10
-
This package uses [Taskflow](https://github.com/taskflow/taskflow) to organize and perform robotics tasks. Each of the tasks in the system will take a ProcessInput which is just a Tesseract::ConstPtr and references to instructions and the seed.
9
+
### TaskInput
10
+
This package uses [Taskflow](https://github.com/taskflow/taskflow) to organize and perform robotics tasks. Each of the tasks in the system will take a TaskInput which is just a Tesseract::ConstPtr and references to instructions and the seed.
11
11
12
-
Each Task will operate on the instructions and the results will get stored in the seed. The ProcessInput does not own the instructions in order to keep it lightweight and able to be segmented into sub-ProcessInputs (see [] operator). Therefore, the instructions and seed passed into the ProcessInput must be kept alive by the user.
12
+
Each Task will operate on the instructions and the results will get stored in the seed. The TaskInput does not own the instructions in order to keep it lightweight and able to be segmented into sub-TaskInputs (see [] operator). Therefore, the instructions and seed passed into the TaskInput must be kept alive by the user.
13
13
14
-
It is also worth noting that ProcessInput is not inherently thread-safe. Since taskflow will attempt to execute as many tasks in parallel as possible, it is the responsibility of the user to ensure that Tasks that use the same portions of the ProcessInput are not running at the same time. In practice, this shouldn't be difficult as many of the planning operations currently implemented have a clear order. However, you should not, for example, try to plan the same segment using two different planners at the same time without first making a copy of the inputs to the ProcessInput for each Task.
14
+
It is also worth noting that TaskInput is not inherently thread-safe. Since taskflow will attempt to execute as many tasks in parallel as possible, it is the responsibility of the user to ensure that Tasks that use the same portions of the TaskInput are not running at the same time. In practice, this shouldn't be difficult as many of the planning operations currently implemented have a clear order. However, you should not, for example, try to plan the same segment using two different planners at the same time without first making a copy of the inputs to the TaskInput for each Task.
15
15
16
16
### Class Structure
17
17
The package is divided into several types of classes
Copy file name to clipboardExpand all lines: tesseract/tesseract_planning/tesseract_process_managers/include/tesseract_process_managers/core/process_info.h
Copy file name to clipboardExpand all lines: tesseract/tesseract_planning/tesseract_process_managers/include/tesseract_process_managers/core/process_planning_future.h
Copy file name to clipboardExpand all lines: tesseract/tesseract_planning/tesseract_process_managers/include/tesseract_process_managers/core/task_generator.h
+19-19
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
/**
2
-
* @file process_generator.h
2
+
* @file task_generator.h
3
3
* @brief Process generator
4
4
*
5
5
* @author Matthew Powelson
@@ -23,8 +23,8 @@
23
23
* See the License for the specific language governing permissions and
0 commit comments